'%20d='M64%205c-3%2018-15%2026-13%2043-9-5-13-13-13-22C20%2043%2015%2062%2022%2082c7%2022%2023%2037%2042%2041%2022-4%2039-21%2043-43%203-17-3-32-18-45%202%2011%200%2018-6%2025C84%2036%2075%2019%2064%205Z'%20/%3e%3cpath%20fill='url(%23heat)'%20d='M64%2045c-2%2015-14%2022-13%2038-5-4-8-9-9-15-7%2010-8%2020-4%2030%205%2012%2014%2020%2026%2023%2013-3%2023-12%2027-25%203-11%200-20-8-29%200%207-2%2012-6%2016%201-16-5-27-13-38Z'%20/%3e%3c!--%20The%20glasses%20render%20as%20two%20stacked%20stroke%20groups:%20a%20pale%20warm%20casing%20under%20a%20dark%20warm-charcoal%20stroke.%20The%20casing%20keeps%20the%20dark%20strokes%20legible%20where%20they%20leave%20the%20flame%20body%20(temple%20tips,%20lower%20rims)%20on%20dark%20backgrounds,%20and%20reads%20as%20a%20rim%20light%20against%20the%20flame%20on%20light%20ones.%20--%3e%3cg%20fill='none'%20stroke='%23ffe3ae'%20stroke-opacity='0.85'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20stroke-width='14'%20d='M7%2063c12-4%2027-5%2043-1M78%2062c16-4%2031-3%2043%201'/%3e%3crect%20x='12'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='14'/%3e%3crect%20x='70'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='14'/%3e%3cpath%20stroke-width='13'%20d='M57%2066c5-4%209-4%2014%200'/%3e%3c/g%3e%3cg%20fill='none'%20stroke='%2333221b'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20stroke-width='8'%20d='M7%2063c12-4%2027-5%2043-1M78%2062c16-4%2031-3%2043%201'/%3e%3crect%20x='12'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3crect%20x='70'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3cpath%20stroke-width='7'%20d='M57%2066c5-4%209-4%2014%200'/%3e%3c/g%3e%3c/svg%3e){kind=small}
@happyvertical/smrt-fields
Layered field policy: per-field defaults, visibility tiers, labels, help, ordering, and organization locks resolved over the code seed at app, tenant, and user scope.
What it gives you
Layered field policy: per-field defaults, visibility tiers, labels, help, ordering, and organization locks resolved over the code seed at app, tenant, and user scope.
- 01Code seed, app, tenant, and user layers resolved into one policy per object
- 02Generated forms that render only the fields present in both the manifest definition and the resolved policy
- 03A form gear and an organization control panel behind two dedicated permissions
How resolution works
Four layers merge low to high: the code seed from @field({ ui }), app rows, the tenant chain, then the signed-in user. A column left empty inherits from the layer below and resetting a customization deletes the row.
Read the field policy guide →Building forms
PolicyField adopts an existing form incrementally; ObjectForm renders the fields present in both the generated definitions and the resolved policy.
Build a policy-aware form →Running it in production
The form gear, the organization control panel, the two permissions, and the difference between a personal preference and an organization rule.
Operate field policies →API and semantics
Exported functions and types, the canonical object reference format, the default-value wire contract, write validation, and caching.
Field policy API →A recipe for form customization
The package declares the fields.form-customization recipe, emitted into the manifest and knowledge recipes with its own user-facing help. It declares a server runtime.
Package UI
Component catalog and public contracts
Browse by the job you are doing. Each group shows its focused import path; the Playground tab renders the working controls and composed patterns.
Policy-aware form primitives
Wrap the inputs a hand-written form already has. Outside a provider PolicyField renders its children verbatim, so a form can adopt policy one field at a time.
@happyvertical/smrt-fields/svelteGenerated object forms
Build a create or edit form from generated browser field definitions and a resolved policy. Alternatively, register every generated collection once. Let each form request its object reference.
@happyvertical/smrt-fields/sveltePolicy administration
The per-form gear for organization and personal overrides, and the tenant-wide control panel that replays the resolved layers.
@happyvertical/smrt-fields/sveltePackage previews
Try the working views
These previews are owned by the package and use its public components. Mock mode is intended for safe browsing; live mode appears only where the package supports it.
Generated interface
REST
The exact route set comes from each model's @smrt({ api }) policy
and the application manifest—not from a second controller definition.
Policy rows are not a browsable resource, and FieldPolicy generates create, update, and delete routes. It also generates the resolve, editor-state, and policy-audit collection actions. Generated list and get remain closed because the model is not tenant-scoped. Unrestricted reads would enumerate every tenant and user row. The generated CLI mirrors that shape and is writes-only. MCP is closed entirely.
Generated interface
MCP
AI tools are generated from the methods you explicitly include. Their inputs are validated against the same model metadata used by REST and CLI.
Policy rows are not a browsable resource, and FieldPolicy generates create, update, and delete routes. It also generates the resolve, editor-state, and policy-audit collection actions. Generated list and get remain closed because the model is not tenant-scoped. Unrestricted reads would enumerate every tenant and user row. The generated CLI mirrors that shape and is writes-only. MCP is closed entirely.
Browser-native agent interface
WebMCP
The generated web definitions carry the same tool names, descriptions, and JSON Schema
inputs as MCP. smrt-web registers them with document.modelContext.
Policy rows are not a browsable resource, and FieldPolicy generates create, update, and delete routes. It also generates the resolve, editor-state, and policy-audit collection actions. Generated list and get remain closed because the model is not tenant-scoped. Unrestricted reads would enumerate every tenant and user row. The generated CLI mirrors that shape and is writes-only. MCP is closed entirely.
Generated interface
CLI
The app CLI turns manifest resources into predictable operator commands while keeping package-specific actions close to their models.
Policy rows are not a browsable resource, and FieldPolicy generates create, update, and delete routes. It also generates the resolve, editor-state, and policy-audit collection actions. Generated list and get remain closed because the model is not tenant-scoped. Unrestricted reads would enumerate every tenant and user row. The generated CLI mirrors that shape and is writes-only. MCP is closed entirely.