Forms & Inputs
Atomic primitives in the forms & inputs family. Click any tile for the live render, the spec it was built from, and the code that fell out.
▓ READY FOR COMPOSITION ▓
- matches /SPEC-\d{3}/
- followed by colon + space
- begins with imperative verb
- P @platformPlatform Engineering
- S @securitySecurity & Compliance
- D @data-engData Engineering
- M @ml-researchML Research
- G @governanceSpec Governance
— ↑/↓ to navigate · ⏎ to commit —
— click to edit · ⏎ commit · esc revert —
— enter executes · ⌃c aborts —
— handles are unique per workspace —
- form-control
- governance
- audit
— backspace on empty pops the last chip —
— enter for next bullet · empty bullet + enter exits —
— ⏎ commits · blur commits —
— fuzzy match across name + tags —
— exposed values are never logged —
— middle bytes never render to the dom —
— grows to 140px then scrolls —
- 01
- 02
- 03
- auth
- oauth
- security
- session
- spec frontmatter complete
- acceptance criteria listed
- failure modes enumerated
- threat model reviewed
- A
- .
- .
-
— governance gate · review at 67+ —
band — HIGH · auto-accept eligible
cost — slower, fewer rollbacks
volume — TRICKLE
expires in — 3 days
The framework is real.
The community is forming now.
DoCoDeGo is in Alpha. The framework is documented, the practices are battle-tested at small scale, and the next release is being shaped in public.
If it produces anything, it should produce engineers and teams who think more clearly about what they are building and why.
Discord is where specs are debated, the framework gets sharper, and decisions land in writing. The conversation is the artefact.