Explore the documentation graph Generated artifacts Background registry
Generated artifacts
Start with the documents, then follow each document into the sections, source specs, and governed assets that explain why the page exists.
README.md
This protected block is the default adoption exemplar: keep the surrounding README hand-authored, generate one useful section from source specs, and let grounded render --check catch drift.
docs/getting-started.md
Start a project with Grounded, add one useful spec, and run the basic validation and rendering loop.
docs/concepts.md
Explain the source-of-truth, metamodel, registry, typed tag, and generated-view concepts that Grounded uses.
docs/cli-reference.md
List the Grounded CLI commands and the canonical workflow decisions that own their behavior.
docs/incremental-adoption.md
Show how to adopt Grounded in small steps without turning the whole project into documentation theatre.
docs/llm-workflows.md
Explain how agents should use Grounded search, specs, generated context, and audits during project work.
docs/drift-checks.md
Explain the checks Grounded uses to make documentation drift visible and reviewable.
docs/PUBLISHING.md
Explain how generated documentation and the Todo demo are built and published.
skills/audit-grounded-knowledge-graph/SKILL.md
Render the standard audit skill from its canonical maintained source.
This protected block is the default adoption exemplar: keep the surrounding README hand-authored, generate one useful section from source specs, and let grounded render --check catch drift.
Start a project with Grounded, add one useful spec, and run the basic validation and rendering loop.
Explain the source-of-truth, metamodel, registry, typed tag, and generated-view concepts that Grounded uses.
List the Grounded CLI commands and the canonical workflow decisions that own their behavior.
Show how to adopt Grounded in small steps without turning the whole project into documentation theatre.
Explain how agents should use Grounded search, specs, generated context, and audits during project work.
Explain the checks Grounded uses to make documentation drift visible and reviewable.
Explain how generated documentation and the Todo demo are built and published.
Render the standard audit skill from its canonical maintained source.
Grounded core models project memory as authored specs that use registry_type definitions. A spec is an authored instance of one registry_type; a registry_type describes what that class of specs is allowed or expected to contain; registry_unit is the minimal base contract for every authored Grounded unit; and knowledge_unit is a richer documented registry_unit for human-facing concepts, rules, types, and decisions. The registry_unit base requires stable identity, type or kind, name, and lifecycle status, with optional owner and summary metadata. Documentation fields such as description and tags belong on documented types. Evidence and relationship fields such as references, examples, tests, and generic links must be opted into by specific registry types rather than inherited from the root base or knowledge_unit. Type-specific JSON Schemas, verification bindings, rendering templates, graph links, and search fields are configured by registry_type definitions rather than hardcoded domain semantics.
Generated project documentation presents project-owned domain units as the primary index.html entry page. Grounded concepts, project memory guardrails, and generated-system metadata remain available on a separate background page through a non-prominent link.
Generated unit pages render structured fields and typed details before implementation data. Raw JSON remains available for debugging and traceability, but it is hidden by default behind a disclosure control.
Governs the README and documentation diagram that shows Grounded specs producing generated docs, LLM context, validation, verification, and drift reports.
Governs the README diagram that compares scattered project knowledge with Grounded-owned canonical facts.
Governs the README diagram that shows Grounded's incremental adoption ladder.
Governs the README image that previews generated Todo example documentation.
Defines the Single owner for durable facts rule so agents and maintainers know when and how to apply it.
Defines the Agents maintain Grounded during project work rule so agents and maintainers know when and how to apply it.
Defines the Semantic slices may nest and overlap rule so agents and maintainers know when and how to apply it.
Explains the Grounded theory concept and how it should be used as canonical Grounded knowledge.
Explains the Grounded project memory concept and how it should be used as canonical Grounded knowledge.
Explains the Bounded modeling slice concept and how it should be used as canonical Grounded knowledge.
Explains the Semantic slice concept and how it should be used as canonical Grounded knowledge.
Documents the spec, registry_type, registry_unit, and knowledge_unit relationship so maintainers know the minimal base contract and documented extension shape for authored Grounded units.
Documents the Separate project domain docs from Grounded background decision and explains how it guides Grounded behavior or project maintenance.
Documents the Render structured fields before raw JSON decision and explains how it guides Grounded behavior or project maintenance.
Documents the Model invariants as explicit concepts decision and explains how it guides Grounded behavior or project maintenance.
Documents the Model statuses as lifecycle values decision and explains how it guides Grounded behavior or project maintenance.
Documents the Provide search on every generated HTML page decision and explains how it guides Grounded behavior or project maintenance.
Documents the Keep unit metadata unobtrusive decision and explains how it guides Grounded behavior or project maintenance.
Documents the Render related concepts inline on unit pages decision and explains how it guides Grounded behavior or project maintenance.
Documents the Color-code links by unit type decision and explains how it guides Grounded behavior or project maintenance.
Documents the Show object type as quiet context decision and explains how it guides Grounded behavior or project maintenance.
Documents the Render typed context as dedicated sections decision and explains how it guides Grounded behavior or project maintenance.
Documents the Model lifecycle vocabularies as lifecycle types decision and explains how it guides Grounded behavior or project maintenance.
Documents the Model concrete nouns as business entities decision and explains how it guides Grounded behavior or project maintenance.
Documents the Model collections as business entities decision and explains how it guides Grounded behavior or project maintenance.
Documents the Render entity invariants from backlinks decision and explains how it guides Grounded behavior or project maintenance.
Documents the Use friendly status value labels decision and explains how it guides Grounded behavior or project maintenance.
Documents the Model status values as lifecycle values decision and explains how it guides Grounded behavior or project maintenance.
Documents the Attach invariants to constrained units decision and explains how it guides Grounded behavior or project maintenance.
Documents the Hide decisions from domain link panels decision and explains how it guides Grounded behavior or project maintenance.
Documents the Link resolvable field types decision and explains how it guides Grounded behavior or project maintenance.
Documents the Keep status values on lifecycle page decision and explains how it guides Grounded behavior or project maintenance.
Documents the Adopt compact docs shell decision and explains how it guides Grounded behavior or project maintenance.
Documents the Componentize generated docs with Lit decision and explains how it guides Grounded behavior or project maintenance.
Documents the Package examples as standalone projects decision and explains how it guides Grounded behavior or project maintenance.
Documents the Initialize project files under .grounded decision and explains how it guides Grounded behavior or project maintenance.
Documents the Make AGENTS updates opt-in decision and explains how it guides Grounded behavior or project maintenance.
Documents the Keep built-in types minimal decision and explains how it guides Grounded behavior or project maintenance.
Documents the Bundle default stylesheet decision and explains how it guides Grounded behavior or project maintenance.
Documents the Add optional grounded-link label decision and explains how it guides Grounded behavior or project maintenance.
Documents the Field rows expose stable anchors decision and explains how it guides Grounded behavior or project maintenance.
Documents the Use optional short names for display decision and explains how it guides Grounded behavior or project maintenance.
Documents the Harden generated outputs and render checks decision and explains how it guides Grounded behavior or project maintenance.
Documents the Require exact type matches and collision checks decision and explains how it guides Grounded behavior or project maintenance.
Documents the Render enum values on enum pages decision and explains how it guides Grounded behavior or project maintenance.
Documents the Support project-defined tags with tag pages decision and explains how it guides Grounded behavior or project maintenance.
Documents the Expose a reusable unit core template decision and explains how it guides Grounded behavior or project maintenance.
Documents the Render explicit slice documentation pages decision and explains how it guides Grounded behavior or project maintenance.
Documents the 0.3.0 version bump so the release version has a canonical Grounded owner.
Documents the constrained inline rich-text syntax so prose fields can link to canonical Grounded units without allowing arbitrary HTML.
Documents the 0.4.0 version bump so the inline rich-text release has a canonical Grounded owner.
Documents the compact list components so generated docs can show dense linked name-and-description rows without full unit cards.
Documents the 0.5.0 version bump so the compact list release has a canonical Grounded owner.
Documents the default documentation font-size token scale so the bundled stylesheet remains readable and aligned with the design brief without project overrides.
Documents the reusable Lit component extraction from a project-specific analytics documentation mock.
Documents the 0.6.0 version bump so the reusable documentation component release has a canonical Grounded owner.
Documents the Graphviz DOT CLI export so Grounded relationship graphs can be generated from the same canonical registry references used by rendered docs.
Documents the 0.7.0 version bump so the Graphviz relationship graph CLI release has a canonical Grounded owner.
Documents the GitHub Pages preparation for generated Grounded documentation and the Todo demo so publishing uses generated artifacts without committing rendered site files.
Documents the light and dark theme toggle for generated Grounded documentation so theme behavior has a canonical owner.
Documents DESIGN.md as the default rendered HTML styling source so bundled docs styling has a canonical owner.
Documents the 0.8.0 version bump so the publishing, theme toggle, and DESIGN.md styling release has a canonical Grounded owner.
Documents the 0.9.0 version bump so the graph presentation and generated documentation navigation release has a canonical Grounded owner.
Documents the CLI search workflow so LLM agents can discover existing entities, concepts, and specs before creating new specs.
Documents the 0.10.0 version bump so the CLI project-memory search release has a canonical Grounded owner.
Documents the project-memory module boundary so graph semantics remain independently testable and JSON, filesystem, and JSON Schema mechanics can be replaced by adapters.
Documents the registry_type nomenclature for Grounded metamodel types and how generated views should label them.
Documents the registry inspection CLI command so maintainers and agents can see both registry types and authored specs from one entry point.
Documents the 0.13.0 version bump so registry inspection and metamodel terminology changes have a canonical Grounded release owner.
Documents the documentation-graph model so generated docs are projections over source specs instead of hand-maintained durable knowledge.
Documents generated document write modes so Grounded can migrate safely from protected generated blocks to fully generated documentation files.
Documents the generated documentation redesign so Grounded pages communicate the underlying graph and source meaning before showing implementation metadata.
Documents the PyPI publication preparation so package metadata, release workflow behavior, and trusted-publishing setup have a canonical Grounded owner.
Documents the 1.0.0 major version bump so the PyPI-ready release has a canonical Grounded owner.
Documents the P2 semantic compression boundary so Grounded exposes fewer public modeling concepts while preserving internal registry precision.
Documents the P3 edge-model decision so Grounded can normalize important relationships without replacing every field with graph machinery.
Documents the runtime efficiency and scope contract for verification and audit execution so repeated proof commands and generated-site rendering stay bounded.
Documents the config contract for opting Markdown files into generated-document coverage without forcing every Markdown file to be managed.
Documents the governed audit skill artifact so Grounded knowledge-graph review guidance has one canonical source and one rendered skill output.
Documents the focused CLI context command so LLM agents can gather bounded, graph-aware project memory from a specific starting point.
Documents the 1.1.0 version bump so the focused context CLI release has a canonical Grounded owner.
Defines the generic binding model so context packs can expose implementation and test artifacts without making every knowledge unit inherently bound.
Documents the 1.2.0 version bump so declared-binding changed-file context lookup has a canonical Grounded owner.
Documents the 1.2.1 version bump so suffix collection field type linking has a canonical Grounded owner.
Documents the Render slice memberships as grounded-links decision and explains how it guides Grounded behavior or project maintenance.
Defines the README problem section from governed source specs and the before-and-after diagram asset.
Defines the README section that points readers to the registry inspection command as a way to understand the active documentation graph.
Defines the README section that summarizes Grounded's source-of-truth value from canonical source specs.
Defines the README section that summarizes the CLI workflow capabilities from command-owning decisions.
Defines the documentation section that explains the safe migration path toward generated public documentation.
Defines the README section that shows a small source spec example.
Defines the README quick start section as ordered setup and render steps.
Defines the README section that suggests good first Grounded specs.
Defines the README command table for common Grounded CLI workflows.
Defines the README section that introduces typed tags and constrained references.
Defines the README adoption diagram section with governed alt text.
Defines the README adoption ladder as structured generated documentation.
Defines the README section that describes when Grounded is and is not a good fit.
Defines the README link list for examples and deeper documentation.
Defines the README section that shows the default Grounded project layout.
Defines the README section that summarizes generated documentation publishing.
Defines the drift checks guide section that lists the main validation, audit, and verification guardrails.
Defines the LLM workflows guide section that explains agent responsibilities from canonical rules and decisions.
Defines the publishing guide section that summarizes publishing and generated documentation release decisions.
Defines the migration example that shows a handwritten README section becoming a protected generated block sourced from specs.
Defines the focused context workflow guidance for LLM agents and maintainers.
Groups the generated public documentation artifacts that Grounded should render and check together.
Defines the trust-status vocabulary used to describe claim credibility separately from lifecycle status.
Provides a concrete example for PROJECT-RULE-001 so the rule can be understood and verified in context.
Defines the protected README command block so the repository entrypoint can stay hand-authored while one useful section is projected from Grounded source specs.
Defines the generated getting-started guide as a projection over setup, first-spec, command, and layout sections.
Defines the generated concepts guide as a projection over Grounded metamodel and documentation graph specs.
Defines the generated CLI reference as a projection over command and CLI workflow sections.
Defines the generated incremental adoption guide as a projection over adoption and first-spec sections.
Defines the generated LLM workflows guide from agent maintenance and search workflow source specs.
Defines the generated drift checks guide from validation, audit, verification, and generated-view guardrails.
Defines the generated publishing guide from GitHub Pages and release-oriented documentation decisions.
Defines the rendered Grounded knowledge-graph audit skill as a generated artifact sourced from the maintained skill source and governing decision.
Defines the guardrail for specs that declare explicit bindings without a bindable type capability.
Defines the guardrail for duplicate binding identifiers within one spec.
Defines the guardrail for malformed explicit binding declarations.
Defines the guardrail for mapped binding fields whose values do not match their declared cardinality.
Defines the guardrail for malformed type-registry binding_field_mappings metadata.
Defines the guardrail for binding targets whose kind is not supported by the current binding slice.
Defines the guardrail for binding roles outside Grounded's supported binding-role vocabulary.
Defines the guardrail for file binding paths that are empty, POSIX-absolute, Windows drive-prefixed, UNC-absolute, home-relative, parent-traversing, or escape the project root.
Defines the guardrail for file bindings whose configured path_exists validation points at a missing repository file.
Defines the guardrail for type definitions that declare unsupported capability names.
Defines the guardrail for type definitions that declare binding field mappings without opting into bindability.
Defines the binding-schema guardrail so implementation files, tests, commands, and other external artifacts remain opt-in bindings rather than universal knowledge_unit fields.
Defines the Pathless SpecRegistry compatibility unit guardrail so compatibility adapters report source models that cannot be represented by the filesystem-shaped legacy SpecRegistry API.
Defines the concept specificity guardrail so concept specs remain sharply defined instead of absorbing arbitrary project prose.
Defines the Required canonical fact lacks declared test coverage guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the decision-shape guardrail so decision specs do not become arbitrary workflow, generated-doc, or implementation-note containers.
Defines the documentation graph typed-reference guardrail so generated document views remain explainable and sections, documents, sets, and assets reference the expected kinds.
Defines the sourced projection guardrail so generated documents and document sections do not become ungrounded prose buckets.
Defines the generated document projection-contract guardrail so each generated output declares how Grounded renders and writes it.
Defines the generated documentation coverage guardrail so configured Markdown roots stay owned by generated_document specs instead of drifting as independent sources of truth. Projects opt in additional roots through grounded.yml, while the generated docs tree remains covered by default through the built-in managed_markdown_roots setting owned by GROUNDED-DECISION-068.
Defines the document-section truth boundary so generated document sections organize projections without becoming canonical claim owners.
Defines the Generated view is stale guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the authored edges container shape so typed relationships enter the registry through a predictable list field.
Defines the authored edge entry contract so each edge has enough structure to normalize and diagnose.
Defines the canonical typed-edge vocabulary so authored edges, JSON Schema, tests, rendering, and search use the same relationship names.
Defines the target-resolution rule for authored and normalized edges.
Defines the verified_by edge semantics so proof-bearing relationships cannot point at arbitrary specs.
Defines generated-artifact edge semantics so documentation and projection nodes derive from or document source specs without becoming canonical truth.
Defines the illustrated_by target-kind rule so visual support is governed by asset specs.
Defines generated-artifact exclusion rules for strong semantic edges.
Defines the optional dependency-layer vocabulary used for depends_on direction checks.
Defines optional semantic_layer dependency direction for depends_on edges.
Defines the backlink ownership rule so inverse relationships are computed from normalized edges instead of maintained by hand.
Defines compatibility between existing relationship fields and the normalized typed-edge model.
Defines the extension-point guardrail so project-specific behavior stays in registries, schemas, template overrides, styles, slice metadata, or verification specs instead of core Grounded internals.
Defines the Duplicate canonical ID guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Invalid JSON spec guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Unknown spec kind guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the public naming guardrail so Grounded's release, package, documentation, generated views, examples, skills, templates, workflow text, tests, and source package public text use one canonical vocabulary.
Defines the Possible duplicate fact ownership guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Unknown reference guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Unknown structured reference guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Unknown example reference guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Unknown artifact reference guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Reference target missing required typed tag guardrail so validation and maintenance work can recognize constrained-reference drift.
Defines the Spec root is not an object guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Missing ID or kind guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Missing required fields guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Reference field is not a list guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Reference list contains non-string values guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Type-specific schema validation failed guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the public vocabulary boundary so generated documentation presents Grounded through a small set of user-facing concepts.
Defines the semantic category guardrail so registry types can be grouped without introducing a large public inheritance hierarchy.
Defines the Specs directory is missing guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Missing central stylesheet guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Missing design tokens guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Hard-coded presentation outside style source guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Unknown typed tag type guardrail so validation and maintenance work can recognize typed tag registry drift.
Defines the Unknown typed tag value guardrail so validation and maintenance work can recognize typed tag vocabulary drift.
Defines the Malformed tag list guardrail so validation and maintenance work can recognize invalid tag shapes.
Defines the invalid trust-status guardrail so validation can report claim credibility values outside the governed vocabulary.
Defines the verified-claim proof guardrail so validation can report verified claims with no active targeted verification.
Defines the invalid verification reference guardrail so validation can report verified claims linked to inactive or non-verification specs.
Defines the verification target-mismatch guardrail so validation can report verified claims linked to proof for a different target.
Defines the generated-artifact truth boundary so projected documentation artifacts cannot satisfy claim credibility.
Defines the checkable trust-status guardrail so checkable claims either link to a targeted verification or explain why the verification is not wired yet.
Defines the observed trust-status guardrail so observed claims cite a non-generated source, evidence text, or an explicit observed basis.
Defines the trust-status guardrail so claim credibility is modeled independently from active, draft, and retired lifecycle state.
Defines the verified-claim proof guardrail so active verified claims must link to active verification specs that target the claim.
Defines the command-existence guardrail so active verification specs must declare a non-empty command whose first executable can be resolved during validation.
Defines the runtime verification-result guardrail so grounded verify records in-memory results and fails when a verified claim's linked verification does not pass.
Defines the Invalid type registry JSON guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Invalid type registry root guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Invalid type definition guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Unknown parent type guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Missing type schema path guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Invalid type schema JSON guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Invalid type schema root guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Invalid JSON Schema for type guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the Invalid tag type registry guardrail so validation and maintenance work can recognize malformed tag type declarations.
Defines the Tag constraint on non-reference field guardrail so validation and maintenance work can recognize invalid reference_tag_constraints configuration.
Defines the Type hierarchy cycle guardrail so validation and maintenance work can recognize circular type inheritance in the merged type registry.
Defines the semantic category validation guardrail so registry type definitions cannot introduce unapproved type families.
Defines the Verification command failed guardrail so validation, audit, and maintenance work can recognize this class of drift.
Defines the verification timeout guardrail so runtime verification cannot hang indefinitely.
Defines the runtime verification target-mismatch guardrail so grounded verify can report proof linked to the wrong target.
Defines the verified-claim runtime proof guardrail so grounded verify fails when linked verification results do not pass.
Records the registry_type schema gap for project-specific fact shapes so future registry or renderer work has a canonical owner.
Records the Semantic slice structure schema gap so future registry or renderer work has a canonical owner.
Binds GROUNDED-DECISION-029 to an executable test so Grounded can verify the documented behavior.
Binds GROUNDED-DECISION-030 to an executable test so Grounded can verify the documented behavior.
Binds GROUNDED-DECISION-031 to an executable test so Grounded can verify the documented behavior.
Binds GROUNDED-DECISION-032 to an executable test so Grounded can verify the documented behavior.
Binds GROUNDED-DECISION-033 to an executable test so Grounded can verify the documented behavior.
Binds GROUNDED-DECISION-034 to an executable test so Grounded can verify the documented behavior.
Binds GROUNDED-DECISION-035 to an executable test so Grounded can verify the documented behavior.
Binds GROUNDED-DECISION-036 to an executable test so Grounded can verify the documented behavior.
Binds GROUNDED-DECISION-037 to an executable test so Grounded can verify the documented behavior.
Binds GROUNDED-DECISION-001 to an executable test so Grounded can verify documented units declare their purpose while the registry_unit base stays minimal.
Binds GROUNDED-DECISION-039 to an executable test so Grounded can verify inline rich-text links render safely and participate in reference validation.
Binds GROUNDED-DECISION-041 to an executable test so Grounded can verify compact list components render linked names and descriptions.
Binds GROUNDED-DECISION-043 to an executable render test so Grounded can verify the generated bundled stylesheet includes the readable design-brief body font token.
Binds GROUNDED-DECISION-045 to an executable render test so Grounded can verify reusable Lit documentation components are emitted and consume design tokens.
Binds GROUNDED-DECISION-047 to an executable CLI test so Grounded can verify Graphviz DOT export includes outgoing and incoming relationships with bounded depth and type filters.
Binds GROUNDED-DECISION-050 to executable render tests so Grounded can verify the theme toggle is emitted with stylesheet token support.
Binds GROUNDED-DECISION-051 to executable render tests so Grounded can verify the bundled stylesheet includes DESIGN.md color, type, and radius tokens.
Binds GROUNDED-DECISION-054 to executable CLI tests so Grounded can verify search, specs --uses, and check-new behavior.
Binds typed tag rendering, tag type registry validation, and reference tag constraints to focused unit tests.
Binds generated link hover tooltip behavior to the renderer round-trip test so generated docs expose target summaries without navigation.
Binds the adapter-backed project-memory loading decision to focused business-module and JSON adapter tests.
Binds GROUNDED-DECISION-057 to an executable test so Grounded can verify the documented naming behavior.
Binds GROUNDED-DECISION-001 to an executable test proving registry_unit does not require documentation or evidence fields at the root.
Binds GROUNDED-DECISION-058 to an executable CLI test proving registry output includes registry types and authored specs.
Binds GROUNDED-DECISION-060 to an executable renderer test proving generated_document specs write protected README blocks and manifest entries.
Binds documentation graph guardrails to executable audit tests proving wrong typed edges, missing write modes, unmanaged Markdown docs, and ungrounded sourced sections are reported.
Binds the semantic generated-docs redesign to an executable renderer test proving generated documents, decisions, the document graph, and the artifact index render content-first views.
Binds PyPI publishing preparation to an executable test proving package metadata, Apache-2.0 license declaration, project URLs, typed-package marker, console entry point, and trusted-publishing workflow configuration are declared.
Binds the current release decision to an executable test proving pyproject metadata and the package __version__ value stay synchronized.
Binds the public naming guardrail to an executable tracked-file scan so public surfaces cannot reintroduce previous project-name vocabulary.
Binds the trust-status vocabulary, verified-claim proof requirement, verification command checks, and runtime verification-result semantics to focused executable tests.
Binds the P2 semantic compression guardrails to tests covering semantic categories, generated-artifact truth boundaries, trust-status structure, concept drift, and document-section projection semantics.
Binds the P3 typed-edge guardrails to tests covering vocabulary, authored edge shape, legacy normalization, target-kind validation, semantic layers, manual backlink warnings, rendering, and search.
Binds the default verification scope, opt-in test-binding verification, verification command deduplication, and audit rendered-site reuse decision to focused executable tests.
Binds the managed_markdown_roots config contract to the audit test proving Grounded only checks Markdown under configured roots.
Binds the governed Grounded knowledge-graph audit skill artifact to its deterministic format verification script.
Binds GROUNDED-DECISION-070 to executable CLI tests proving context seed resolution, changed-file binding resolution, graph traversal, Markdown output, JSON output, bounds handling, retired seed filtering, invalid argument rejection, and registry issue refusal.
Binds the opt-in binding model to executable tests proving knowledge_unit stays thin, bindable types can declare explicit bindings, non-bindable specs cannot declare bindings, registry-declared file and test fields normalize to binding metadata, unsafe paths and invalid cardinality fail clearly, Windows-style absolute, drive-prefixed, and home-relative paths are rejected, unsupported target kinds preserve their declared kind, context JSON separates relations from bindings, Markdown renders repo-relative binding paths without artifact content, JSON omits binding metadata unless requested, human commands surface registry warnings, JSON commands stay machine-clean, and optional missing test bindings become structured diagnostics.
Binds PROJECT-RULE-001 to an executable test so Grounded can verify the documented behavior.
Binds PROJECT-RULE-003 to an executable test so Grounded can verify the documented behavior.
Binds PROJECT-DECISION-001 to an executable test so Grounded can verify the documented behavior.
Defines the deterministic verification command for the rendered Grounded knowledge-graph audit skill format.
Defines the verification command that scans tracked public surfaces for previous project-name vocabulary before release.
Defines the verification command for the trust-status and verified-claim credibility loop.
Defines the verification command for PROJECT-RULE-001 so project checks can be run consistently.
Describes the Scope a bounded Grounded model workflow so agents and maintainers can follow the expected process.