The authoring workflow
The complete local loop from product idea to immutable review handoff.
The loop
idea
→ authoring interview
→ standalone project
→ fixtures + implementation
→ Workbench / Connector Lab
→ conformance
→ immutable archive + digest
→ private review
→ owner-only install
→ later compatible releasePackage project
The Author plugin creates a directory shaped like this:
my-experience/
├── chasing-mastery.authoring.json
├── chasing-mastery.package.json
├── chasing-mastery.listing.json
├── package.json
├── src/
├── fixtures/
└── .chasing-mastery/
├── run.sh
├── run.ps1
├── toolchain.json
└── toolchain/The .chasing-mastery directory is project-local infrastructure. Authors use
its scripts through ordinary package commands; they do not install or maintain
a global Chasing Mastery CLI.
Commands
| Command | Purpose |
|---|---|
npm run cm -- status | explain the project and missing proof |
npm run cm -- workbench | open the real package artifacts and fixtures |
npm run cm -- conformance | validate schemas, behavior, authority, and claims |
npm run cm -- ready | produce deterministic archive, digest, and handoff |
npm run cm -- evolution --from previous.cmpkg | classify compatibility against exact prior bytes |
The precise scripts can vary with the scaffolded project, but every operation resolves through its pinned local toolchain.
Proof is product work
Fixtures are not test debris. They explain the contract:
- the normal completion path;
- every meaningful terminal result;
- malformed or unauthorized input;
- repeated/delayed intent and idempotency;
- stale connection and recovery;
- reduced motion and multiple viewports;
- manual and automatic equivalence;
- progression boundary values;
- correction and retraction when supported;
- coordination or narration edge cases when declared.
Workbench should show the same thing a member or viewer will see while driving the actual immutable code—not a second author-only renderer.
Review is independent
ready means ready for review, not approved or publicly listed. The host
replays the archive in isolation, verifies its digest and declared capabilities,
and creates an owner-private listing only after review succeeds. Public
community publication remains a separate moderated operation.