Browse
Decisions
Architectural, product, and process decisions as records.
Entries
- Adopt Self Replace For Forma CLI Updates
Use self-replace as the cross-platform executable replacement layer while Forma owns release identity, verification, explicit authorization, transient recovery, and CLI contracts.
knowledge/decisions/adopt-self-replace-for-forma-cli-updates.md - Keep Structured Schema Validation Explicit Before Automatic Check Integration
Keep schema.validate as the manual Forma CLI MVP and defer artifact declarations and automatic forma check integration until repeated workspace evidence justifies a compatible opt-in model.
knowledge/decisions/defer-automatic-schema-check-integration.md - Defer Forma Core Host Abstraction And WASM Runtime
Defer a broad Forma Core host abstraction and WASM runtime migration until a concrete Host use case justifies the cost.
knowledge/decisions/defer-forma-core-host-abstraction-and-wasm-runtime.md - Define CLI And Editor Compatibility Window
Replace exact CLI and editor package equality with an explicit protocol and capability contract while retaining a safe legacy fallback.
knowledge/decisions/define-cli-editor-compatibility-window.md knowledge/decisions/editor-extension-primary-product-surface.mdknowledge/decisions/forma-p0-core-architecture.mdknowledge/decisions/resolve-authored-config-into-typed-workspace-model.md- Use Markdown Workspace Entrypoint
Use `.forma.md` as the only Forma workspace configuration entry before public release.
knowledge/decisions/use-markdown-workspace-entrypoint.md knowledge/decisions/use-settings-driven-taxonomy-and-navigation-model.mdknowledge/decisions/use-space-as-core-partition-model.mdknowledge/decisions/webapp-primary-gui-client.md