internal/

Decision-conflict report: computed section (03 §Decision-conflict gate, "Computed section — declared-edge completeness").

Package artifact is the contract package (02-artifact-contract.md): ref grammar, common and per-kind frontmatter schemas, and the record schemas (verdi.annotation/v1, verdi.board/v1, verdi.evidence/v1, verdi.rollup/v1, verdi.deviation/v1).

Package artifactview holds the per-kind frontmatter projection every artifact-rendering surface needs beyond internal/index.Entry's generic view: owners, frozen/provenance stamps, and every feature-spec-only field (class, story, declared boundaries, acceptance criteria, the I-5 dispositions block).

Package atomicfile provides the one shared atomic-write primitive for the store's mutable-zone files (spec/shared-homes ac-1).

Shared JSONL I/O for annotation streams (02 §Record schemas): reading every record out of one stream file, enumerating a whole mutable/annotations/ directory, locating the right stream for a given target or board, and appending one record.

Package boardlayout is the zoned, incremental, position-stable board layout algorithm (05 §Workbench "Layout": objects without a stored coordinate are grouped by kind, ordered by document/ID order, and slotted into their zone's next free position; stored coordinates are never moved by generation).

Package bundle assembles a derived evidence bundle — the four files at data/derived/<ref-slug>/<commit>/ (01 §Directory layout) — from already strict-decoded upstream artifacts (internal/upstream) and a service's verdi.bindings.yaml sidecar (internal/artifact).

Package canonjson implements the canonical JSON form used for every generated, digest- or integrity-hashed artifact in the store (PLAN.md I-18, mirroring upstream verdi-go's own canonjson): object keys sorted, no HTML escaping, and a trailing newline.

Package commitdesign implements the mechanical half of the commit-to-design ritual (05 §Workbench, PLAN.md ledger I-20): given a board's pins/stickies/yarn, write a draft feature spec skeleton (story, placeholder AC, `context:` from the board's pinned refs) on the current design branch, a frozen `board.json` snapshot committed alongside it (design provenance, one frame — never a drag history), and a `dispositions:` block listing every sticky as `open-question` — legal, honest, and VL-014-lint-clean until the commit-to-design skill (or a human) upgrades each entry to `incorporated` or `contradicted`.

Actor projection (authority design §4): the manifest's `actors` section is a canonical projection of already-sealed governanceprincipal.PrincipalResolution values, never a reconstitutable one.

Top-level `verdi audit` orchestration (05 §CLI, R4-I-10): the exemption audit (backlinks.go, autofile.go) plus V1-P3's spec-stale surfacing (internal/evidence.SpecStale), one pass over the corpus.

Package designinterview is `design start`'s flagless TTY interview (spec/cli-creation ac-2, ledger L-N7): given no --problem/--outcome/ --defer-statements at all, on an attached terminal, design start collects the class template's own statement fields interactively — driven from the exact same placeholder-enumeration descriptors (internal/designscaffold.Fields) the board's creation form already reuses to validate its own submissions (spec/creation-form ac-1), one field contract, two front ends, never a second hand-rolled field list.

Package designprovenance defines ASD's committed, append-only, non-authoritative design-provenance sidecar.

Package designscaffold is the shared spec-scaffolding core, promoted out of cmd/verdi/design.go (CLAUDE.md: "anything used by two or more packages lives in a shared internal/ package ...

Package dex implements `verdi dex build` (PLAN.md Phase 12, 05 §Verdi-dex): a static site that is a pure function of the store's committed tree at a given commit — byte-identical across rebuilds of the same tree state, with every page honestly labeled with its temporal class (01 §Temporal classes) rather than silently claiming currency it cannot back up.

Package diagrambase is the digest-verified base-recovery seam a derived proposal's mechanical before-peek and reset stand on (spec/board-editor ac-4, dc-5; spec/diagram-proposals ac-3): recover the pinned base's source from git history at derived_from.ref's pinned commit, compute sha256 over the base's canonical graph JSON, and return the base bytes EXACTLY — or a typed, disclosed error and NO bytes.

Package diagramedit is the board editor's structural-op → text-edit grammar (spec/board-editor ac-2/ac-3, dc-2): each operation — add-node, connect, rename, delete-node, delete-edge — is a PURE function of (source bytes, operation) to source bytes.

Package diagramverify turns a `class: proposal` diagram's authored mermaid body into a comparable, truth-checked structure (spec/verification-extractor, implementing spec/diagram-proposals ac-1).

Package disclosure implements the shared disclosed-unproven rendering seam spec/disclosure-legibility#ac-1 requires and docs/spikes/v1/ disclosure-enumeration-spike.md specifies: every disclosure-producing call site already computes the same three-valued judgment (proven / violated / disclosed-unproven, CLAUDE.md constitution 2) on demand; what was missing was a shared shape and one render function so that judgment reads in one consistent vocabulary wherever it appears, rather than as N independently hand-authored strings that can silently drift apart on the next edit (spec/disclosure-seam's own rung-3 finding — see conflict/disclosure-seam-rename-insufficient).

Package disclosureview is the one disclosures view over the internal/disclosure seam (spec/disclosures-panel, implementing spec/disclosure-legibility#ac-2's "one view"): a fresh, never-persisted enumeration of the checkout's current disclosures (Current) plus the single shared item/empty-state markup both editions consume (HTML) — the workbench's live page and the dex's read-only, main-only edition render through these same two functions, never a private reimplementation (05 §Lenses: "computed the same way — no separate logic path", the law the story-page ladder badges already obey).

Package draftmutation implements ASD's structured, authority-gated, crash-safe proposal mutation kernel.

Package evidence implements 03 §The fold: the deterministic reduction of a story's acceptance-criteria evidence records, waivers, and attestations into a per-AC status and a story-level eligibility verdict.

Package execworkspace implements spec/execution-workspace (ledger SI-10, SI-15): the deterministic <workspace-id> identity and state grammar for the two materialization request shapes, and the operations over it — materialization, release, the gc slice, and isolation-profile construction.

Package experiment implements the comparative-spike-experiments (CSE) artifact schemas: strict decode and validation for every versioned CSE artifact (spec/comparative-spike-experiments AC-1, AC-2, DC-2..DC-5, DC-12..DC-14, CO-1..CO-4, CO-7), canonical normalization and definition identity, derived lifecycle state, and candidate/observation integrity checks.

Package experimentapp composes the closed CSE schemas, policy decision, accepted Git facts, capability discovery, and result verification ports.

Package experimentdecision implements the comparative-spike-experiments (CSE) closed deterministic recommendation engine (spec/comparative-spike-experiments AC-2, DC-4, DC-5, DC-6, DC-12, DC-14, CO-1, CO-3, CO-5, CO-7): given one locked github.com/jyang234/verdi/internal/experiment.Definition, a complete, integrity-valid observation set, and the execution layer's environment-policy attestation for the run (SI-42), Evaluate deterministically produces exactly one experiment.Result expressing proven-winner, violated-with-witness, or disclosed-unproven, in the registered evaluation order.

Package experimentevaluator runs the one strict CSE evaluator command protocol through an already-authorized execution-workspace profile.

Package experimenthuman verifies offline, action-bound human proofs for experiment operations without reading ambient identity or credentials.

Package experimentpolicy owns the strict CSE experiment_execution payload and its commutative reduction after Context Integrity selects applicability.

Package experimentrun derives and validates the sealed inputs to one CSE execution run.

Package filelock implements I-12's per-checkout writer-lock algorithm as a shared primitive (CLAUDE.md: "anything used by two or more packages lives in a shared internal/ package").

Package fixturegit builds deterministic git repositories for tests, from a declarative list of (files, commit-message) layers.

Comment-thread round-trip (V1-P7): three port methods list an MR/PR's full comment feed, post a token-bearing comment, and query per-thread resolution state — 05 §Review stickies and forge round-trip.

Package gitx is a minimal set of git plumbing helpers, execed rather than linked (no cgo, no go-git dependency — PLAN.md §2: "internal/gitx/ ...

Package governanceprincipal is the shared governance-principal kernel: the single strict governance-profile schema, canonical principal identifiers and resolution, advisory attribution records, and the one authorization interpretation every governed surface consumes (GLG v3 AC-3, DC-16..DC-25; CI v2 AC-1, DC-17..DC-23; owner rulings OD-1/OD-2).

Package httpjson is the shared HTTP-JSON transport seam (spec/forge-transport ac-1, dc-1): the one place that builds an outbound JSON request, applies a caller-supplied auth/header hook, bounds the call with a deadline, hands the completed round trip to a caller-supplied status classifier, and decodes a successful response.

Package humanartifact is the shared human-artifact extension contract and scaffold-resolution seam spec/context-integrity-v2 AC-1 requires: "The operating model resolves a configurable scaffold for every committed human-authored artifact kind: policies, overlays, exemptions, feature, story, and component specs, ADRs, obligations, attestations, waivers, reaffirmations, and future model-registered human kinds.

Package index implements the semantics 01 §Scale and 02 §Link taxonomy / §External refs own: a walk of the committed zone that decodes every artifact through internal/artifact, the in-memory index built from that walk plus internal/store's service discovery (external-ref minting for boundary contracts, obligations, and OpenAPI docs), backlink inversion of the link taxonomy, and a stdlib full-text search over id/title/body.

Package initwizard is the interview logic behind `verdi init --wizard` (spec/init-wizard, ledger L-N5, design doc §12 rules W-1..W-4/W-3b), kept separate from cmd/verdi/init.go's verb plumbing (CLAUDE.md: "one package = one concern"): this package owns the Q&A state machine, the candidate model's live validation preview, and materializing content (verdi.yaml, model.yaml, template overrides) into an ALREADY-STAGED root.

Package instructionprojection generates and verifies the harness instruction files (AGENTS.md, CLAUDE.md, and future adapter-declared equivalents) that a constitution store's adapters project (spec/ context-integrity-v2 AC-1: "AGENTS.md, CLAUDE.md, and future harness files are generated projections of the constitution.

Package journey defines Verdi's canonical journey record: GLG AC-1's stable output contract for `verdi journey`, its workbench projection, MCP, and dex (.verdi/specs/active/guided-lifecycle-governance-v3/ spec.md, AC-1, DC-2/DC-3/DC-4, CO-4).

Package lint is artifactlint: the VL-001..VL-020 rules (see engine.go's allRules for the authoritative registry) from 02 §Lint rules, run over a store root's committed zone plus whatever git and service-discovery context each rule needs.

Adapts Backend.Forge over workbench.CommentFeed for get_board's review-mode mirror (05 §MCP server's get_board row: "mode-appropriate annotations a human sees in `verdi serve`" — the review-comment feed is the fourth projection input, 05 §Workbench "Board as projection").

Package model implements verdi.model/v1 (ledger L-M1, docs/design/plans/2026-07-17-extensibility-phase1-plan.md Task 5; reference shape: docs/design/concepts/2026-07-17-integration-startup- guide.md §5.2, Appendix C tables C-2/C-3): the operating model's one declared source.

Package policyartifact implements the artifact grammar of the constitution store under .verdi/policy/ (spec/context-integrity-v2 AC-1, DC-3, DC-4, DC-20, DC-23, DC-24; store-layout §Directory layout's policy/ entry, whose internal grammar SI-6 assigns to the policy-authority unit): strict decoding, semantic validation, normalization, canonical encoding, and digesting for the policy, policy-overlay, policy-exemption, and policy-constitution artifact kinds, plus the storage record for governance-profile artifacts whose schema and decoding the governance-principal kernel owns (OD-1, DC-20 — this package stores, identifies, and digests profiles; it never decodes or interprets their rule content itself).

Package policyauthority is the constitution store's one loader and one effective-policy resolver (spec/context-integrity-v2 DC-23; owner ruling OD-5: "Context Integrity exclusively owns policy storage, inheritance, effective-policy resolution, and policy identity/digest.

Package policyintegration holds this delivery unit's cross-package AC-1 integration proofs.

Package provider defines the story-provider port (docs/design/specs/04 §The port): the consumer-defined interface verdi uses to resolve story metadata from an external tracker and publish AC rollups back to it, one-way.

Package readinesspilot derives the Wave 3.5 in-memory readiness snapshot.

Package reclaim implements spec/gc-reclaim's sweep: `verdi gc --reclaim-unmanaged`'s eligibility predicate (ac-1) and its execution engine (ac-2), consuming *internal/residue.Result directly rather than re-deriving any of its facts from git independently (dc-1) — the audit's report and gc's plan are the SAME computation, internal/residue.Scan, read by two different verbs, never computed twice.

Package refindex computes the directory index spec/workbench-directory ac-2 needs — every spec on the default branch and every unmerged design branch's draft — as a pure function of git ref state (spec/ref-index).

Package render holds the markdown-and-code rendering machinery shared by every HTML-producing surface (internal/dex's static site, internal/ workbench's server-rendered pages): goldmark (GFM) plus chroma syntax-highlighting at render time, and the I-5 dispositions-block table renderer ("workbench and dex render the block as a table so humans never read raw YAML" — 05 §Workbench, I-5).

Package repositoryfacts defines the shared, canonically encoded repository-identity fact shape SI-85 extracts from internal/journey: remote origin, branch, HEAD, configured default branch, their relationship, dirty/staged posture, managed-worktree identity, and which checkout state an evaluated target's bytes came from (context-compiler authority design §4).

Package residue implements spec/closure-hygiene's scan: `verdi audit`'s third, additive report section (dc-1) naming every git-reality-versus- spec-status contradiction (AC-1), every stranded `close/<name>` branch (AC-2), and a read-only survey of merged-but-undeleted branches and worktrees (AC-3) — never a guess where git state cannot decide, never a mutation.

Package runtimeprobe implements spec/runtime-evidence's scheduled-probe mechanism (dc-1), resolving true-closure's oq-1 and delivering its own ac-3: every evidence kind a spec can declare — runtime included — needs a producing mechanism queryable by (story, AC) at close time (03 §Runtime evidence residence).

Package specstate derives a specification revision's effective lifecycle state — proposed, accepted-pending-build, superseded, closed, or unproven — from candidate bytes plus Git history on the configured default branch (docs/superpowers/specs/2026-08-01-merge-signals-spec- acceptance-design.md, "Merge-Signaled Specification Acceptance").

Package store implements the semantics 01-store-layout.md owns: store manifest decode, root discovery (I-16), the normative ref-slug mapping (01 §notes), the corpus tree hash and cache key naming (I-15, D4), and service discovery via .flowmap.yaml (01 §Store manifest, PLAN.md §3 "Service discovery" row).

Package storyresolve resolves a user- or tool-supplied story/spec argument to a decoded active feature spec, per I-30's strict two-form contract.

Package stubinstantiate is the shared core for creating a story (or spike) spec from a feature's declared stub, via pure git plumbing that never touches the calling checkout's HEAD, working tree, or index (spec/scoping-canvas ac-6) — the mechanism both the board's stub-instantiate action (internal/workbench/boardspecapi.go) and `verdi design start --from-stub` (cmd/verdi/design.go, spec/ cli-creation ac-3, ledger L-N7) call, so the two surfaces can never drift (the ADJ-65 asymmetry closed at the mechanism, not merely at the surface).

Package upstream execs the pinned verdi-go toolchain (module github.com/jyang234/golang-code-graph, binaries cmd/flowmap and cmd/groundwork) and strict-decodes its JSON output (PLAN.md §3, I-4).

Package wallbadge computes the board wall's badges (spec/badge-computes, spec/wall-receipts): VL lint findings partitioned by their own wall-locus self-classification (lint.Finding.Locus, dc-3), the spec-stale/pending-supersession ladder flags through the EXACT exported entry points internal/dex/lens.go's story-lens uses — never a second, drifting logic path (co-3) — and the size-smell observation (spec/case-file-flags ac-2: dc-1's deterministic viewport proxy, an observation and never a rule).

The board page (05 §Workbench): cards (pinned refs), stickies (annotations, including board-only ones per I-34), yarn (proto-links), positions — autosaved via POST to data/mutable/boards/<story>.json, never committed per-drag.

Package wtmanager is spec/worktree-manager's backend seam: lazily cutting, reusing, and reclaiming a managed git worktree per local design branch, entirely under a checkout's data zone.