0.0.8
A second sweep of every page settled 127 findings: a story lands on main whole, secrets stay away from agents, and an agent names every decision of its own for a veto. A project that is set up imports the index in its entry point and links the commands there, renames its tickets to lead with their id, rebuilds its pick script as the merge script, and switches off its agent's commit attribution. Nothing in it is stable yet.
- 202 standards in 21 modules: one added and 87 changed
- The update script runs as written, on Python 3.9 and up
- An update carries a changed overview line, and names every changed tool spec to rebuild from
- The unlink script drops the overview line of a standard the project did not adopt
- The coentrify.json example keeps the healing log its automatic healing writes to, and the page names the values of
workflowandrecords - An idea takes the Always modules of the recommendations and a workflow, and the stack modules join once it is built
- The first prompt in a fresh project carries the source. Once it is set up, the entry point leads to the commands at the source: a project that is set up adds that to its entry point
- A standard from coentrify that a project changes, by healing too, turns customized, and a game's new law goes in its own docs
- The commit gate refuses a piped check saved to a variable, and passes the shape the standard teaches and a tag listing with
--sort - A story lands on main whole once its tickets are done, in one merge commit that carries its id: the simplified release workflow. A project on the tickets workflow rebuilds its pick script as the merge script of the Landing spec
- A builder rebases its story onto main and runs the main checks green before it merges, so the conductor only merges
- A violation the change introduced is fixed. One that was there, small and obvious in a touched file, is fixed too. One that is complex or out of scope is noted as debt. A fix of what was there is named for a veto
- The docs are synced with the build and land with the story. The director's feedback on an agent's decision comes back as rework
- Content an agent fills in is written and named for a veto. An impactful change, one that adds scope or moves a rule or a decision away from the director, is discussed first
- A rename updates every reference at once, and a changed convention sweeps its existing occurrences as debt. A pattern from a review goes to healing
- Automatic filing files at once, and a change to a module with a source of its own reaches coentrify only when it is generic, as an addition
- In the tickets workflow, healing files a heal ticket,
HEAL-1, which carries its go when healing is automatic - Work that changes what the user sees or hears is filed as a feature or a bug, never as debt
- The plan lists stories, never their tickets, and a builder takes its story's tickets in the story's order. A blocked story waits for its blocker's verdict
- The entry point imports the index next to the Core Rules, so every agent and subagent knows the modules: a project that is set up adds the import
- A maybe is an idea the director phrases with uncertainty, and a go names ready work by id, by story or for all that is ready
- A prototype's ticket is its one piece of tracking, a test written failing first is no bug, and a plan a change conflicts with is filed as a question
- A secret is set up so only the running app reads it, never in a
.envfile, a chat or a log. A release build is signed, and on a Mac notarized, in CI without the keychain - An agent starts its processes so it can find them again, and reads the full command line of each before a kill
- The docs agent grooms under a docs ticket of its own, a story stays on the plan as long as its builder works it, and a debt story's builder ends at its merge
- A version closes on the director's word, and its batch is the work merged since the last tag
- A ticket is squashed into one commit on its story's branch, under the story's merge commit
- A follow-up only the director can do goes on an optional, short list of director tasks
- An e2e run gets its port as an argument, never an exported variable, and an agent tells its own listener by the marker in its command line
- The examples no longer disable a submit button on invalid input, and Barrel Imports' overview line matches its rule
- Each app of a workspace has its docs in
docs/<app>/, and the quiet launch keeps its store page unpublished as long as the store allows - Claude Code reads the entry point and its imports again after a compaction, so the reload hook is built only for an agent that does not
- A ticket's file name leads with its id,
feat-214-upload-retries.md: a project renames its tickets once. A file whose name a template fixes keeps it - The inbox holds raw ideas, easily scrapped, and the roadmap the decided ones by priority
- The DEV day counts the days with a commit, the day turning at 04:00, and lives in Changelog Per Version
- A debt story's merge line names its Veto lines, a dropped ticket, a workshop and an epic are archived, and Game Design files its tickets for their own phase
- The game cadence follows the director's order and the inboxes' order, the wiki cleanup is filed at each version's close, and the records file feedback where the project's workflow says
- A real backend is proved by its own spec test, a missing token is added to the project's layer, and a use case has one name in its spec and its test
- A project lists the libraries it contributes to under
librariesincoentrify.json, and their friction is filed there - A plan keeps its items' status, and
architecture.mdholds how it is built, never the wiring - A change to the wiki's tree is workshopped first, and a move within a section is done and named. The spec's Overview case changes before its test
- A use-case id may change, renamed everywhere at once, as when a feature takes its module as a prefix
- A shared component takes no application-specific branch, not even one. The mock contract is One Artifact Per File's one exception, and the ui examples follow No Magic Values
- A game runs no tests while prototyping, reports only what stands outside a ticket, and tracks a Concept prototype by its ticket
- A game's version closes on the director's go, and the day may go on. Alpha's fine-tuning epics are passes, and a level needs the interface it needs
- The player sees the distance to the next goal, AFK Safe's index line keeps what the player set running, and a view in the Application Template has no route
- A styles folder is named after its alias, its parent on the load path. Data depends on core and config, and the styles split between ui and the app's shell. The default alias is
@ui - A mock's interface is named with an
Interfacesuffix - The laws are checked before a feature's spec, Lore and Game tickets get a verdict, First Playable is built on Feature tickets, and a check keeps the devbox out of a release
- Gamedev brings the tickets workflow, the activity log and playtests, the styleguide sweep works with any tooling, and the wiki keeps one config file
- The wiki sorts the record groups newest first, a reel never takes the default video size, and E2E Assert Before Interacting says why it asserts first
- A one-app project's plan is the plan itself, a healing entry follows its change's commit, and an unbuilt feature carries its mark under Features
- Endpoints and environment URLs live in concern docs of their own under
docs/workspace/ - A spec is any written specification, at any level, and a scalar constant takes its plain type
- The template attribute order is the project's lint setting, a header pairs with a footer and a top with a bottom, and a capture is labeled by its ticket
- A wind-down starts no new builder and logs everything, early access is gated by content and a closed beta by who plays, and every browser engine runs muted
- A wrong line in an outside skill is fixed in a standard, a builder works its story without re-reading it per ticket, and an app that updates itself keeps its updater's files
- Gestures In Tests gives the real reason mobile users tap send, a prototype is measured by when the director can see or try it, and a changelog names a packaged build only for an app that ships packages
- A workspace serves a product and its audience, a foreshadowing hint is designed in the product's narrative, and a still hides the app frame the game draws
- The phase gate is defined once, in Project Lifecycle, Parallel Agents links The Builder instead of restating it, and Incremental Pacing's count is an example
- File A Change holds the issue shape, and the Roadmap Template links Work Item Names
- The game workflow pages, Workspace Levels and Reels And Video Proof link the rules they copied
- The setup switches off the agent's own commit attribution: a project that is set up adds
attributionto its agent's settings
Angular
Architecture
- Changed App-Shield
- Changed Per-Application Split Over Shared Branching
Behavior
- Changed A Maybe Is A Trigger To Investigate
- Changed Code Review Compounds Into Patterns And Sweeps
- Changed Communication Boundary
- Changed Docs Hold Only What The Director Decided
- Changed Don't Introduce Tech Debt
- Changed Feature Workflow
- Changed File A Change With Coentrify
- Changed Flag Every Addition Of Your Own
- Changed Non-Destructive Documenting And Test Automation
- Changed Own Ports, Own Processes
- Changed Propagate Renames And Convention Changes Everywhere
- Changed Prototype Mode Is Speed First
- Changed Reload The Standards After Compacting
- Changed Standards Maintenance
- Changed Standards Over Skills
- Changed Sync The Docs After Every Change
Code
- Changed Code Principles
- Changed Pre-Empt Recurring Code-Review Nits
Commits
- Changed Commits
- Changed Gate Commits On Exit Codes
- Changed Main Stays Green, Work Stays Clean
Docs
- Changed Application Template
- Changed Docs Are Hierarchical, Explicit And Short
- Changed Docs Describe Behavior, Not Wiring
- Changed Docs Folder Structure
- Changed Feature Spec Template
- Changed File Names
- Changed Library Feedback
- Changed Workspace Levels
- Changed Workspace Template
E2E
- Changed E2E Assert Before Interacting
- Changed E2E Test Conventions
- Changed E2E Tests Must Demonstrate Behavior
- Changed Per-Feature Overview Test
Electron
- Changed Electron Packaging And Suite
Gamedev
- Changed Captures And Reels
- Changed Devbox
- Changed Game Design Laws
- Changed Game Design Laws: Progress
- Changed Game Phases
- Changed Game Phases: Concept
- Changed Game Phases: Design
- Changed Game Phases: Development
- Changed Game Work Workflow
- Changed Gamedev Working Cadence
- Changed Incremental Pacing
- Changed Launch Strategy
- Changed Silent Runs
Records
- Changed Activity Log
- Changed Changelog Per Version
- Changed Healing Log
- Changed Playtest Files
- Changed Request Log
Reporting
- Changed Reels And Video Proof
Security
- Added Keep Secrets Away From Agents
- Changed Never Access The Keychain
Simple Workflow
- Changed Plan Template
- Changed Plans Vs Persistent Files
- Changed Roadmap Template
- Changed The Simple Workflow
Tests
- Changed Bracket State Changes With Contrast Assertions
- Changed Gestures In Tests
Tickets Workflow
- Changed Agent Roles
- Changed The Builder
- Changed Building A Ticket
- Changed The Conductor
- Changed Stabilize Before Adding
- Changed Ticket Template
- Changed Work Tracking
- Changed Work Workflow
Tooling
- Changed Develop Against Mocks
- Changed Parallel Agents
- Changed Playwright Video Recording
- Changed Start Playwright On A Clean Port
- Changed VitePress Wiki
TypeScript
- Changed Barrel Imports
- Changed No Magic Values
- Changed One Artifact Per File
UI
- Changed UI Components First
- Changed UI Layout Via Slot Composition
- Changed UI Styleguide
- Changed UI Variants By Function, Not By Color
- Changed Walk The User's Journey
Web
- Changed Always Use Design Tokens For Colors
- Changed SCSS Shared Partial Imports