gcf-aif-ext 0.4.1 → 0.5.1

package/profiles/unit-entity.md

@@ -8,10 +8,10 @@ format: cnlp-format.md
 mood: declarative
 
 headings:
-- none: the body is flat; the `## <id>` line and the header fields above the blocks name the unit
+- none: the body is flat; in design/ the `## <id>` line and the header fields above the blocks name the unit, in work/ the frontmatter does
 
 frontmatter_fields:
-- none: an entity never becomes a card, so its header lives above the blocks in design/
+- none: in design/ the header lives above the blocks; in work/ the work item schema holds the frontmatter
 
 lexicon_exempt:
 - none: every block is read when the entity is planned and coded
@@ -44,5 +44,5 @@ custom_sections:
 - none: a block that is not listed above is prose looking for a home
 
 enforcement:
-- `ai-factory gcf design check`, over the units in gcf/design/
+- `ai-factory gcf design check`, over the units in gcf/design/ and the items in gcf/work/
 - the gcf pre-commit hook runs the same check and refuses a commit with a blocking finding

package/profiles/unit-mechanic.md

@@ -1,6 +1,6 @@
 ---
 name: unit-mechanic
-description: The CNL-P profile of a GCF design unit of type mechanic — one body for its section in design/<system>.md and for its card in cards/<id>.md.
+description: The CNL-P profile of a GCF design unit of type mechanic — one body for its section in design/<system>.md and for its work item in work/<id>.md.
 ---
 
 format: cnlp-format.md
@@ -8,22 +8,10 @@ format: cnlp-format.md
 mood: declarative
 
 headings:
-- none: the body is flat; in design/ the `## <id>` line and the header fields above the blocks name the unit, in cards/ the frontmatter does
+- none: the body is flat; in design/ the `## <id>` line and the header fields above the blocks name the unit, in work/ the frontmatter does
 
 frontmatter_fields:
-- schema
-- id
-- type
-- title
-- status
-- system
-- depends
-- pillars
-- source
-- reopens
-- tune_count
-- built_at
-- created
+- none: in design/ the header lives above the blocks; in work/ the work item schema holds the frontmatter
 
 lexicon_exempt:
 - none: every block is read when the unit is planned, built or played
@@ -69,12 +57,12 @@ sections:
 - key: contract
   form: bullet-list
   required: yes
-  note: card stage, absent in design/ - paths and entry points, never member lists or values; an architecture rule is a constraint
+  note: work stage, absent in design/ - paths and entry points, never member lists or values; an architecture rule is a constraint
 
 - key: interactions
   form: bullet-list
   required: yes
-  note: card stage, absent in design/ - "<other id>: how the two cross", one line per crossing
+  note: work stage, absent in design/ - "<other id>: how the two cross", one line per crossing
 
 - key: constraints
   form: bullet-list
@@ -107,5 +95,5 @@ custom_sections:
 - none: a block that is not listed above is prose looking for a home
 
 enforcement:
-- `ai-factory gcf design check`, over the units in gcf/design/ and the cards in gcf/cards/
+- `ai-factory gcf design check`, over the units in gcf/design/ and the items in gcf/work/
 - the gcf pre-commit hook runs the same check and refuses a commit with a blocking finding

package/profiles/unit-resource.md

@@ -1,6 +1,6 @@
 ---
 name: unit-resource
-description: The CNL-P profile of a GCF design unit of type resource — an economy resource with its sources and sinks, in design/<system>.md and as a card.
+description: The CNL-P profile of a GCF design unit of type resource — an economy resource with its sources and sinks, in design/<system>.md and as a work item.
 ---
 
 format: cnlp-format.md
@@ -8,22 +8,10 @@ format: cnlp-format.md
 mood: declarative
 
 headings:
-- none: the body is flat; in design/ the `## <id>` line and the header fields above the blocks name the unit, in cards/ the frontmatter does
+- none: the body is flat; in design/ the `## <id>` line and the header fields above the blocks name the unit, in work/ the frontmatter does
 
 frontmatter_fields:
-- schema
-- id
-- type
-- title
-- status
-- system
-- depends
-- pillars
-- source
-- reopens
-- tune_count
-- built_at
-- created
+- none: in design/ the header lives above the blocks; in work/ the work item schema holds the frontmatter
 
 lexicon_exempt:
 - none: every block is read when the unit is planned, built or played
@@ -49,12 +37,12 @@ sections:
 - key: contract
   form: bullet-list
   required: yes
-  note: card stage, absent in design/ - paths and entry points, never member lists or values
+  note: work stage, absent in design/ - paths and entry points, never member lists or values
 
 - key: interactions
   form: bullet-list
   required: yes
-  note: card stage, absent in design/ - "<other id>: how the two cross", one line per crossing
+  note: work stage, absent in design/ - "<other id>: how the two cross", one line per crossing
 
 - key: constraints
   form: bullet-list
@@ -87,5 +75,5 @@ custom_sections:
 - none: a block that is not listed above is prose looking for a home
 
 enforcement:
-- `ai-factory gcf design check`, over the units in gcf/design/ and the cards in gcf/cards/
+- `ai-factory gcf design check`, over the units in gcf/design/ and the items in gcf/work/
 - the gcf pre-commit hook runs the same check and refuses a commit with a blocking finding

package/profiles/unit-rule.md

@@ -8,10 +8,10 @@ format: cnlp-format.md
 mood: declarative
 
 headings:
-- none: the body is flat; the `## <id>` line and the header fields above the blocks name the unit
+- none: the body is flat; in design/ the `## <id>` line and the header fields above the blocks name the unit, in work/ the frontmatter does
 
 frontmatter_fields:
-- none: a rule never becomes a card, so its header lives above the blocks in design/
+- none: in design/ the header lives above the blocks; in work/ the work item schema holds the frontmatter
 
 lexicon_exempt:
 - none: every block is read when the rule is planned and tested
@@ -48,5 +48,5 @@ custom_sections:
 - none: a block that is not listed above is prose looking for a home
 
 enforcement:
-- `ai-factory gcf design check`, over the units in gcf/design/
+- `ai-factory gcf design check`, over the units in gcf/design/ and the items in gcf/work/
 - the gcf pre-commit hook runs the same check and refuses a commit with a blocking finding

package/schemas/item.schema.json

@@ -100,6 +100,10 @@
     },
     "model": { "$ref": "#/definitions/textOrNull" },
     "effort": { "$ref": "#/definitions/textOrNull" },
+    "version": {
+      "anyOf": [{ "type": "null" }, { "type": "string", "pattern": "^\\S+$" }]
+    },
+    "channel": { "$ref": "#/definitions/slugOrNull" },
     "created": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$" }
   }
 }

package/skills/gcf-card/SKILL.md

@@ -23,16 +23,17 @@ forbidden_behaviors:
 - do not put `until:` in the frontmatter: it is a line annotation inside slots
 - do not move a section, edit the backlog or write `status:` by hand: `ai-factory gcf take`, `item new`, `done`, `drop` and the item moves own those
 - do not reuse an id: an ended id stays ended; rework gets a new id with `reopens: <old id>`
+- do not remove a D2 record cited as `assumed: q-NNN`: it stays in `gcf/open-questions.md` until its `until:` fires; when the human confirms the value earlier, rewrite each citation to `answer: q-NNN` first
 
 outputs:
 - each answered slot gets a provenance record `- slot: <block>` with `answer: manual`, or `answer: q-NNN` when it closes a question
-- a design-unit item body carries every block of its type plus `contract:` (paths and entry points) and `interactions:` (`<other id>: how the two cross`, or `- none: <why>`)
+- a design-unit item body carries every block of its type; a mechanic or resource item adds `contract:` (paths and entry points) and `interactions:` (`<other id>: how the two cross`, or `- none: <why>`)
 - every item carries a `live:` delta before it ends: what it adds, modifies or removes in `gcf/LIVE.md`, or `none: <why>`
 
 workflow:
 1. for a free-text design idea: ask "into work now, or park it?"; write a unit in the matching `gcf/design/<system>.md` with `source: manual` and `TBD` slots, append `- <id>` to `gcf/backlog.md`, and on "park" stop here
-2. for non-design work: pick the type - tech, bug, spike, asset, content, perf, release - and propose the gate its type gives; the human may flip it (`--gate auto` is "no playtest")
-3. a bug needs `--severity` and a `repro:` the human confirms
+2. for non-design work: pick the type - tech, bug, spike, asset, content, perf, release - among those `ai-factory gcf phase` says the phase takes, and propose the gate its type gives; the human may flip it (`--gate auto` is "no playtest")
+3. a bug needs `--severity` and a `repro:` the human confirms; a release needs `--release <version> --channel <name>` from the human
 4. run `ai-factory gcf item new <id> --type <type> [--gate <gate>] [--parent <feature>] [--title "<line>"]`, add `--from <in-id>` when it comes from the inbox, `--blocked "file needed"` for a final asset; then write `intent:` and `live:` and stop
 5. for a design unit: run `ai-factory gcf where <id>`; the id must be a single unit of `gcf/design/`; read its section from the file the command names
 6. for a unit with `flags: impl?` ask the human first whether the mechanic already ships; on "yes" run `ai-factory gcf drop <id> --reason "already ships"` and stop
@@ -44,7 +45,7 @@ workflow:
 12. write each answer into the unit in place, with its `answer:` provenance record
 13. run `ai-factory gcf design check --json` until the unit's entry in `units` reads `ready: true`, then commit the answered unit
 14. run `ai-factory gcf take <id>` for one unit, or `ai-factory gcf take <id> <id> --feature <feature-id>` to group several under a feature; it writes `gcf/work/<id>.md` and removes the sections and backlog lines in one step
-15. in each design-unit item write `contract:` from the code tree and `interactions:` from the units and items that write the same state; a soft unit whose human wants no playtest gets `gate: auto` - it will close as unplayed
+15. in each mechanic or resource item write `contract:` from the code tree and `interactions:` from the units and items that write the same state; a soft unit whose human wants no playtest gets `gate: auto` - it will close as unplayed
 16. write the item's `live:` delta (a feature's children keep `none: parent`; the feature writes the capability), run `ai-factory gcf design check`, and commit
 17. report the item paths, each item's gate, and for a verdict item the one question the playtest will answer
 

package/skills/gcf-verdict/SKILL.md

@@ -21,7 +21,7 @@ forbidden_behaviors:
 - do not edit systems docs, `LIVE.md`, history or graveyard by hand: the commands own them
 
 workflow:
-1. with no arguments: run `ai-factory gcf playtest` and stop - that list, awaiting-verdict and unplayed items, is the session's playtest sheet
+1. with no arguments: run `ai-factory gcf playtest session` and stop - its build line and checklist of awaiting-verdict and unplayed items are the session's playtest sheet
 2. read the item; for a verdict ask the human the miss_criterion question and record the answer in one line
 3. for `tune` at the tune limit (`tune_limit` in `gcf/config.yml`, 3 by default): the command refuses; the way out is a kill, and a redesigned envelope becomes a new item with `reopens: <id>`
 4. for `keep` of a design-unit item still awaiting its verdict: compress it first - the collapse copies lines verbatim, 1 line per behavior record, refusal and boundary

package/templates/agents-block.md

@@ -1,23 +1,30 @@
-## Game Context Framework (from gcf-aif-ext)
-
 gcf_context:
 - the game's design and its work live in `gcf/`, and the `ai-factory gcf` commands and the gcf skills change them
 - read `gcf/INDEX.md` before anything else under `gcf/`: it lists every subsystem, design unit and work item
 - `gcf/LIVE.md` says what the game does now, and `gcf/PILLARS.md` says what it must stay
+- `ai-factory gcf board --json` gives the whole state in one read: the phase, the items by status with plan progress, the inbox and the open questions
 
 gcf_work:
 - every piece of work is one work item `gcf/work/<id>.md`: find the item before writing code for a feature, a bug or a tech task, or create it with the gcf-card skill
 - a raw idea, a playtest note or a CI finding that is not work yet goes to `ai-factory gcf inbox add "<text>"`, and the gcf-triage skill sorts it later
 - before planning an item, run `ai-factory gcf context <id>` and read only the files it lists under `gcf/`
-- drive a ready item with the gcf-run skill when the project has gcf-harness-aif-ext, otherwise with aif-plan and aif-implement
-- end the work on an item with its command: `ai-factory gcf submit <id>` for gate verdict or decision, `ai-factory gcf close <id>` for gate auto with every check green
+- drive a ready item with the gcf-run skill when the project has gcf-harness-aif-ext (a batch at once: `ai-factory gcf-harness run <ids...>`), otherwise with aif-plan and aif-implement
+- after the code, write the item's `live:` delta and run `ai-factory gcf verify <id>`: fix what it reports and run it again until every check is green
+- then end the work on the item with its command: `ai-factory gcf submit <id>` for gate verdict or decision, `ai-factory gcf close <id>` for gate auto
 - work that cannot go on: run `ai-factory gcf block <id> --reason "<why or the question>"`
+- in a worktree on branch `work/<id>` change no `gcf/` file but the item's `live:`, commit all, then run `ai-factory gcf verify <id> --mark`: `ai-factory gcf integrate` in the main checkout merges it and records the move
 - a design question only the human can answer becomes a D1 record in `gcf/open-questions.md`
+- a word added to a `not:` of `gcf/glossary.md` leaves `gcf/design/` and every item but an unplayed one in the same commit: `ai-factory gcf design check` names each hit as M4
+- the human plays from `ai-factory gcf playtest session`; each free note from that play goes to `ai-factory gcf inbox add --source playtest "<note>"`
+- a release item carries `version:` and `channel:` (`item new <id> --type release --release <v> --channel <c>`): its end writes the `release:` block of `gcf/LIVE.md`
+- `item new` and `take` refuse a type the current phase does not take: run `ai-factory gcf phase` and bring the refusal to the human
+- a pillar changes only on the human's word: `ai-factory gcf pillar rename <from> <to>`, or `ai-factory gcf pillar retire <id> --reason "<why>"`
 
 gcf_forbidden:
 - do not edit `status:`, `frozen:`, `gcf/LIVE.md`, `gcf/history.md`, `gcf/graveyard.md` or `gcf/INDEX.md` by hand: the commands own them
 - do not give a verdict or a decision: `verdict` and `decide` belong to the human, through the gcf-verdict skill
 - do not answer a `TBD` of a design unit yourself: ask the human and offer your draft as the proposed answer
+- do not run `ai-factory gcf phase next`: the phase moves on the human's word only
 - do not reuse an ended id: rework gets a new id with `reopens: <old id>`
 - do not commit past the gate with `--no-verify`: a refused commit names what to fix
 

package/templates/config.yml

@@ -10,6 +10,8 @@ unplayed_warn_after: 5
 plan_passes: 5
 dod_attempts: 2
 # The project's own commands for the auto DoD (Methodology §6); the engine does not matter.
+# gcf verify fails on an empty one; `none` says the project has no such step.
+# Phases (Methodology §10) come from code; a `phases:` list here replaces the whole set.
 dod:
   test:
   build: