Pull compositions from the deal until the expanded catalog ships

The composition pool (stagings) is not ready: too thin to help, and its
draws crowd the decision it rides along with. concept-seed.mjs stops
rendering the staging block by default; IMPECCABLE_COMPOSITIONS=1
re-enables it for catalog development, and the draw machinery,
rating-weighted selection, and mode scoping stay intact and tested for
its return. new-work.md drops the dress-the-staging-challengers
instruction and the FORM contract's staging clauses; the surface-scope
roll still assigns which of the model's own structures gets built.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Paul Bakaus
2026-07-29 17:46:54 -07:00
co-authored by Claude Fable 5
parent 19e400e392
commit bd1763764a
3 changed files with 19 additions and 8 deletions
+2 -2
View File
@@ -36,7 +36,7 @@ Keep the visual system fixed. Derive five to seven materially different structur
`node {{scripts_path}}/concept-seed.mjs --scope surface --mode <mode>`
The script assigns which structure gets built; your top-ranked structure is what every run would ship, so the dice come from outside. Dress its staging challengers in the committed identity and weigh them against your list before building. Never run the script for a local extension or a precisely specified narrow request; shape those directly.
The script assigns which structure gets built; your top-ranked structure is what every run would ship, so the dice come from outside. Never run the script for a local extension or a precisely specified narrow request; shape those directly.
### Create or replace the visual world
@@ -70,7 +70,7 @@ Your measured rendition prior: warm, bookish, family, and child-facing subjects
## 5. Record the decision
Before code, state the chosen direction as a contract in the artifact's opening comment, five short blocks, 150 words at most, in a form that survives the production build: an HTML comment in the emitted markup, never only a templating-frontmatter comment, placed as the first child of the document's body in the root layout, never inside a slotted or child component (some compilers, Astro among them, strip a slot's leading comment while keeping deeper ones). After the first production build, grep the built output for the seed key; a contract the build erased is a contract nobody can audit. THESIS: the one idea this surface owns and the category-default arrangement it refuses. OWN-WORLD: the palette and component language, specific enough to be recognizable with all content removed. STORY: what the visitor understands, believes, and does. FIRST VIEWPORT: the exact composition, what is where and at what scale, and where the primary action sits. FORM: the chosen form, its position on your ordered list, the staging chosen for it, and the seed key the script printed; when the seed dealt stagings, choosing the world does not silently discharge the staging decision, so name the one you commit to. Close the comment with one more line, FINISH: the run's exit condition, verbatim "unreviewed and undocumented is unfinished; this build ends with the finish review, the verdict, and DESIGN.md". The comment tops the artifact you re-open on every edit, the one reminder that survives a long build: a page that looks complete with the FINISH line undischarged is not done, it is abandoned at the finish line. If a block reads like a mood, the direction is not decided yet; the finishing review audits the render against this contract. <!-- rule:skill-decide-then-build -->
Before code, state the chosen direction as a contract in the artifact's opening comment, five short blocks, 150 words at most, in a form that survives the production build: an HTML comment in the emitted markup, never only a templating-frontmatter comment, placed as the first child of the document's body in the root layout, never inside a slotted or child component (some compilers, Astro among them, strip a slot's leading comment while keeping deeper ones). After the first production build, grep the built output for the seed key; a contract the build erased is a contract nobody can audit. THESIS: the one idea this surface owns and the category-default arrangement it refuses. OWN-WORLD: the palette and component language, specific enough to be recognizable with all content removed. STORY: what the visitor understands, believes, and does. FIRST VIEWPORT: the exact composition, what is where and at what scale, and where the primary action sits. FORM: the chosen form, its position on your ordered list, and the seed key the script printed. Close the comment with one more line, FINISH: the run's exit condition, verbatim "unreviewed and undocumented is unfinished; this build ends with the finish review, the verdict, and DESIGN.md". The comment tops the artifact you re-open on every edit, the one reminder that survives a long build: a page that looks complete with the FINISH line undischarged is not done, it is abandoned at the finish line. If a block reads like a mood, the direction is not decided yet; the finishing review audits the render against this contract. <!-- rule:skill-decide-then-build -->
On a new or replacement world, DESIGN.md is written at finish, from the built world, by the shipped documenter (section 7); a rulebook written before the build gets defended against reality instead of describing it, and hands the design-system detector an unstable target. A new world shipped with no DESIGN.md is still an incomplete run. An ordinary extension does not rewrite DESIGN.md. <!-- rule:skill-design-md-from-the-build -->
+11 -5
View File
@@ -427,11 +427,17 @@ ${buildIndex} of your own grounded list; seed key ${key}.
// Field order is the migration: `compositions` is current, `stagings` is what
// the API emitted while these were called stagings, and `staging` is the
// single-pick shape from before it dealt three. Older installs keep working.
const compositions = Array.isArray(data.compositions)
? data.compositions
: Array.isArray(data.stagings)
? data.stagings
: data.staging ? [data.staging] : [];
// Compositions are pulled from the deal until the expanded catalog is
// ready for prime time: the current pool crowds the decision more than it
// widens it. IMPECCABLE_COMPOSITIONS=1 re-enables rendering for catalog
// development; the draw machinery, axes, and grain report stay intact.
const compositionsEnabled = process.env.IMPECCABLE_COMPOSITIONS === '1';
const compositions = !compositionsEnabled ? []
: Array.isArray(data.compositions)
? data.compositions
: Array.isArray(data.stagings)
? data.stagings
: data.staging ? [data.staging] : [];
// The grain report. A top-up keeps the deal at three, which is right, but it
// must not read as three on-target inputs: a flow request answered entirely by
// view-grain compositions means the model has to derive the flow's own
+6 -1
View File
@@ -122,7 +122,12 @@ describe('concept seed scopes', () => {
assert.equal(rendered.status, 0);
assert.match(rendered.stdout, /mode: experience/);
assert.match(rendered.stdout, /--scope direction --mode experience --from stable-test/);
assert.match(rendered.stdout, /FIRST-SURFACE COMPOSITION/);
// Compositions are pulled from the deal by default until the expanded
// catalog ships; the draw machinery stays live behind the env gate.
assert.doesNotMatch(rendered.stdout, /COMPOSITION/);
const gated = run('direction', ['--mode', 'experience'], { IMPECCABLE_COMPOSITIONS: '1' });
assert.equal(gated.status, 0);
assert.match(gated.stdout, /FIRST-SURFACE COMPOSITION/);
});
it('draws several composition inputs from distinct families when the approved pool allows it', () => {