Card Registry — INDEX (Go projection)

Scaffold cards (the nine executable-scaffold patterns)

04The classification axes (layer, mechanism, trigger mode, transfer tag) are language-neutral and carried verbatim from the core catalog so the three projections stay comparable. What differs per row is the checker (a Go tool, not a Rust or TS one) and the per-language Band-3 routine.

Rule cards

05Authored as their checkers ship. The naming card is authored once, in the Rust projection (the shared rule's lineage home); its checker ships on Go too — one engine rule reads Rust #[cell] and Go //spec:cell (rendered by the extract bridge into the same attr) through one parser.

Trigger-mode delivery summary

• 07inline (per-edit, lint-detectable): C, F — go vet / staticcheck / conform findings in the editor loop.
• gate (per-merge): B, D, E, G, H — go build / per-package go test -race / Example execution at the cell's verification gate.
• raid (scheduled/on-adoption): A, I — go:generate regeneration and codemods swept across a layer.
• review (human/strong-agent): none yet; reserved for judgment-heavy cards.

Go checker surface (what each card's checker stands on)

• 08go build / go vet — the compile gate: defined-type nominal safety (B), unused-import/variable hygiene, context placement, printf shapes.
• go test per package, -race — the Class E loop (E); Example functions with // Output: are compiled AND executed (G — a behavioral doctest, stronger than compilation-only).
• go test -fuzz + committed testdata/ seed corpus — the differential engine (D).
• staticcheck / exhaustive — evidence providers (MIT / BSD-2): the unused-code and correctness census, and the closed-set switch exhaustiveness the compiler cannot check (guide §5 — the one rule a linter carries entirely).
• go-ai-native-conform (go-extract facts → conform-core rules) — the structural gate: cell isolation, the §7 ban census (init, ambient defaults, naked go, error-string matching), file budget, seam-error-cites-req in the Class-F grammar.
• codemod post-checks — atomic apply + go build + per-package go test green (I).

09Checker statuses marked shipped land with this package's own toolchain (the GO-AI-NATIVE-PLAN campaign); specified rows await the pilot (research/go-demo is the first carrier — vibevm itself carries no Go until the Kubernetes work begins). A card graduates from BETA when its checker is implemented AND its evidence IDs are non-empty AND pilot evidence has not falsified it.

Axis coverage (research frame A–H)

• 10A language-shape: A (generators), I (codemods)
• B names & tokens: covered by guide §3 (naming + the free nominal types) — rule-closed-vocabulary-naming (shipped cell-name-is-computed, composition only; the closed-vocabulary half of R3-004 stays unbuilt)
• C meta-layer: A, F, G
• D context & repo: covered by guide §2 (cells, closure) — candidate rule-cell-closure
• E verification: B, C, D, E, F, H
• F spec-binding: specmap (PROP-014, guide §8) — mechanism, not a card
• G empirics: G
• H weak-reader: E, H, I

Go-specific additive coverage (beyond the nine)

• 11Goroutine ownership (guide §5) is a Go-specific rule enforced through the ban census (naked_go_in_cell) and review; candidate dedicated card rule-owned-concurrency if pilot triggers warrant.
• The loud-conformance assertion (var _ Seam = (*Impl)(nil), guide §2) rides card B's checker as a presence check; candidate rule-loud-conformance.

Pending cards (named, not yet authored — pilot will prioritize)

• 12rule-cell-closure (R3-001) — cells declare their full semantic dependency set; no ambient state.
• rule-owned-concurrency (guide §5) — every goroutine has an owner; channels are implementation.
• rule-contract-first-ordering (R3-002) — intent before body.
• rule-uniformity (R3-006/H6) — one idiom per operation; mark exceptions.
• antipattern-init-registration (guide §2/§7) — the stdlib-blessed import side effect, banned in cells.
• antipattern-god-file (R3-013) — fan-in per file bounds swarm throughput.
• antipattern-lying-prose (R2C-004/H4) — unverified godoc claims near code.

13These are deferred not because they are unimportant but to honor minimal sufficiency: the nine scaffold cards are the runnable-capital core; rule/anti-pattern cards are added as the pilot shows which triggers actually fire.

Notes on status

• 14shipped = the checker ships in this stack (go-ai-native-conform / go-ai-native) and runs on any consumer tree.
• specified = checker is defined but not yet implemented.
• specified (pilot) = checker defined; implementation is a named pilot task.
• WISH = no checker yet (A5); the card is advisory until one exists.