Views Overview Document Graph Artifacts Background Assets Grounded outputs diagram Before and after knowledge drift diagram Incremental adoption diagram Generated Todo documentation diagram Business Rule Single owner for durable facts Agents maintain Grounded during project work Semantic slices may nest and overlap Concepts Grounded theory Grounded project memory Bounded modeling slice Semantic slice Decisions Registry unit core Separate project domain docs from Grounded background Render structured fields before raw JSON Model invariants as explicit concepts Model statuses as lifecycle values Provide search on every generated HTML page Keep unit metadata unobtrusive Render related concepts inline on unit pages Color-code links by unit type Show object type as quiet context Render typed context as dedicated sections Model lifecycle vocabularies as lifecycle types Model concrete nouns as business entities Model collections as business entities Render entity invariants from backlinks Use friendly status value labels Model status values as lifecycle values Attach invariants to constrained units Hide decisions from domain link panels Link resolvable field types Keep status values on lifecycle page Adopt compact docs shell Componentize generated docs with Lit Package examples as standalone projects Initialize project files under .grounded Make AGENTS updates opt-in Keep built-in types minimal Bundle default stylesheet Add optional grounded-link label Field rows expose stable anchors Use optional short names for display Harden generated outputs and render checks Require exact type matches and collision checks Render enum values on enum pages Support project-defined tags with tag pages Expose a reusable unit core template Render explicit slice documentation pages Release slice and description features as 0.3.0 Support constrained inline rich text Release inline rich text as 0.4.0 Render compact linked item lists Release compact lists as 0.5.0 Increase bundled stylesheet font scale Generalize reusable documentation components Release reusable documentation components as 0.6.0 Generate Graphviz relationship graphs Release Graphviz graph export as 0.7.0 Prepare documentation site for GitHub Pages Add generated docs theme toggle Adopt DESIGN.md default documentation styling Release publishing and documentation styling as 0.8.0 Release graph presentation and sidebar accordions as 0.9.0 Search project memory from the CLI Release CLI project-memory search as 0.10.0 Adapter-backed project-memory loading Name governed type definitions registry types List registry types and specs from the CLI Release registry inspection as 0.13.0 Generate documentation from a documentation graph Support full-file generated document ownership Render generated docs as semantic views Prepare PyPI package publishing Release PyPI-ready Grounded as 1.0.0 Compress public semantics for P2 Introduce minimal typed edges Verification runs reuse repeated work Configure managed Markdown roots explicitly Govern the Grounded knowledge graph audit skill Build focused LLM context from the CLI Release focused context CLI as 1.1.0 Model bindings as opt-in type capabilities Release changed-file context lookup as 1.2.0 Release suffix collection field type links as 1.2.1 Render slice memberships as grounded-links Generated Artifacts Documentation source of truth section Registry inspection section Grounded value proposition section CLI workflow section Documentation migration section Tiny example section Quick start section First useful spec section Common commands section Typed tags section Adoption diagram section Adoption ladder section Usage fit section Examples and deeper docs section Project layout section GitHub Pages publishing section Drift guardrails section Agent workflow section Release publishing section Protected block migration example section Focused context section Generated Artifacts Public documentation set Enums Trust status Example Generated docs reference canonical specs Generated Artifacts README generated document Getting started generated document Concepts generated document CLI reference generated document Incremental adoption generated document LLM workflows generated document Drift checks generated document Publishing generated document Grounded knowledge graph audit skill Guardrails Bindings on non-bindable type Duplicate binding ID Invalid explicit binding shape Invalid mapped binding value Invalid binding field mapping Unsupported binding target kind Invalid binding role Unsafe file binding path Missing file binding path Unknown type capability Binding mapping without bindable capability Knowledge units do not own concrete binding fields Pathless SpecRegistry compatibility unit Concepts avoid catch-all drift Required canonical fact lacks declared test coverage Decisions stay narrow Documentation graph reference has wrong type Sourced document section has no sources Generated document lacks projection contract Documentation file is not generated Document sections are projection assembly Generated view is stale Authored edges field is a list Authored edge entries have type and target Edge type vocabulary stays canonical Authored edge targets must resolve Verified by edges target active proof specs Projection edges do not create truth owners Illustration edges target assets Strong semantic edges do not target generated artifacts Semantic layer vocabulary stays small Dependency layers flow from concrete to stable Manual backlinks are legacy compatibility Legacy fields normalize into typed edges Project behavior must use extension points Duplicate canonical ID Invalid JSON spec Unknown spec kind Grounded public naming guardrail Possible duplicate fact ownership Unknown reference Unknown structured reference Unknown example reference Unknown artifact reference Reference target missing required typed tag Spec root is not an object Missing ID or kind Missing required fields Reference field is not a list Reference list contains non-string values Type-specific schema validation failed Public vocabulary stays compressed Semantic categories stay small Specs directory is missing Missing central stylesheet Missing design tokens Hard-coded presentation outside style source Unknown typed tag type Unknown typed tag value Malformed tag list Invalid trust status Verified claim lacks proof Verified claim references invalid verification Verified claim proof targets another spec Generated artifacts cannot own truth Checkable claims need a structural path Observed claims need a non-generated basis Trust status is separate from lifecycle status Verified claims require targeted proof Verification commands must be runnable-looking Runtime verification proves verified claims Invalid type registry JSON Invalid type registry root Invalid type definition Unknown parent type Missing type schema path Invalid type schema JSON Invalid type schema root Invalid JSON Schema for type Invalid tag type registry Tag constraint on non-reference field Type hierarchy cycle Invalid semantic category Verification command failed Verification command timed out Runtime verification target mismatch Verified claim failed runtime proof Schema Gaps Project-specific fact shapes belong in the type registry Semantic slice structure Test Bindings Grounded link label attribute is rendered and honored Field rows expose anchors and fragment links Knowledge unit short names are used for rendered labels Generated outputs are HTML-safe and render checks report obsolete pages Field types resolve exactly and slug collisions fail fast Enum pages render closed value lists Tagged objects and fields render tag links and grouped tag pages Project templates can extend unit-core and the core unit page renders collection-aware field links Slice pages render scoped members with overrides Documented units require descriptions Rich text links render and validate as references Tag pages render compact item lists Bundled stylesheet uses readable font scale Reusable documentation components are bundled Graph command emits relationship DOT Generated docs include a theme toggle Bundled stylesheet follows DESIGN.md tokens CLI search finds entities and related specs Typed tags validate and constrain references Generated links expose target tooltips Project-memory loading is adapter-backed Registry types render as Grounded Types Registry unit base stays minimal Registry CLI lists types and specs Generated document blocks render from specs Documentation graph audit catches invalid edges Semantic documentation templates render content first PyPI package metadata and publish workflow are declared Package version is synchronized Public surfaces use Grounded naming Trust credibility loop is enforced Semantic compression boundary tests Typed edge model tests Verification and audit reuse repeated work Managed Markdown roots are configurable Audit skill format is verified CLI context builds focused LLM context Binding normalization and context output Bootstrap validation covers single-owner rule Semantic slice nesting is covered by Grounded validation Slice memberships render as grounded-links Verification Audit skill format check Public naming drift check Trust credibility loop tests Bootstrap validation Workflows Scope a bounded Grounded model Document Graph Docs are projections, not sources. Generated documents point to ordered sections. Sections point to durable source specs and governed assets.

Overview Artifacts

 README.md
  1. 1

    Common commands section

    Defines the README command table for common Grounded CLI workflows.

    Generate Graphviz relationship graphsSearch project memory from the CLIBuild focused LLM context from the CLIModel bindings as opt-in type capabilitiesList registry types and specs from the CLI
docs/getting-started.md
  1. 1

    Quick start section

    From a checkout today. After the first PyPI release, install with pipx install grounded or run one-off commands with uvx grounded.

    Initialize project files under .groundedPrepare PyPI package publishingAgents maintain Grounded during project work
  2. 2

    First useful spec section

    Good first candidates are facts that already cause confusion or repeated explanations:

    Single owner for durable facts
  3. 3

    Common commands section

    Defines the README command table for common Grounded CLI workflows.

    Generate Graphviz relationship graphsSearch project memory from the CLIBuild focused LLM context from the CLIModel bindings as opt-in type capabilitiesList registry types and specs from the CLI
  4. 4

    Project layout section

    Defines the README section that shows the default Grounded project layout.

    Initialize project files under .groundedMake AGENTS updates opt-in
docs/concepts.md
  1. 1

    Grounded value proposition section

    These source specs describe the current Grounded value proposition without making README.md the durable owner of those claims.

    Grounded theoryGrounded project memorySingle owner for durable factsAgents maintain Grounded during project workCompress public semantics for P2
  2. 2

    Typed tags section

    Plain string tags are useful for loose grouping. Use typed tags when the classification should be validated.

    Registry unit coreName governed type definitions registry types
  3. 3

    Documentation migration section

    Start with protected generated blocks inside existing Markdown files. Full-file generation remains available for mature docs once the source specs and projection graph are complete.

    Render explicit slice documentation pagesGenerate documentation from a documentation graphSupport full-file generated document ownership
docs/cli-reference.md
  1. 1

    Common commands section

    Defines the README command table for common Grounded CLI workflows.

    Generate Graphviz relationship graphsSearch project memory from the CLIBuild focused LLM context from the CLIModel bindings as opt-in type capabilitiesList registry types and specs from the CLI
  2. 2

    Focused context section

    Use grounded context START when an LLM agent needs bounded project memory before modifying, extending, or reviewing a spec. START may be either an exact spec ID or a search query; exact active spec IDs take precedence. Search-resolved seeds must be verified before treating the pack as authoritative. Use grounded context --changed-files PATH [PATH ...] when the starting point is one or more changed files that should resolve through declared file bindings. The command resolves seed specs, includes those seeds, then includes active related specs up to the requested relationship depth and item limit. When bindable registry types declare bindings, --include-bindings exposes metadata for external artifacts such as implementation and test files. Binding metadata is separate from artifact content; this first slice reports that file contents are not included.

    Build focused LLM context from the CLIModel bindings as opt-in type capabilitiesSearch project memory from the CLI
  3. 3

    CLI workflow section

    Defines the README section that summarizes the CLI workflow capabilities from command-owning decisions.

    Generate Graphviz relationship graphsSearch project memory from the CLIBuild focused LLM context from the CLIList registry types and specs from the CLI
  4. 4

    Registry inspection section

    Defines the README section that points readers to the registry inspection command as a way to understand the active documentation graph.

    List registry types and specs from the CLI
docs/incremental-adoption.md
  1. 1

    Adoption ladder section

    Defines the README adoption ladder as structured generated documentation.

    Agents maintain Grounded during project workBootstrap validation
  2. 2

    First useful spec section

    Good first candidates are facts that already cause confusion or repeated explanations:

    Single owner for durable facts
  3. 3

    Protected block migration example section

    Move durable claims into source specs first, then project a small README block from those specs. The README remains approachable, while CI can run grounded render --check to catch stale generated content.

    Generate documentation from a documentation graphSupport full-file generated document ownershipGenerated view is stale
  4. 4

    Usage fit section

    Use Grounded when:

    Grounded theorySingle owner for durable factsAgents maintain Grounded during project work
docs/llm-workflows.md
  1. 1

    Agent workflow section

    Defines the LLM workflows guide section that explains agent responsibilities from canonical rules and decisions.

    Single owner for durable factsAgents maintain Grounded during project workSearch project memory from the CLIAdapter-backed project-memory loading
  2. 2

    Focused context section

    Use grounded context START when an LLM agent needs bounded project memory before modifying, extending, or reviewing a spec. START may be either an exact spec ID or a search query; exact active spec IDs take precedence. Search-resolved seeds must be verified before treating the pack as authoritative. Use grounded context --changed-files PATH [PATH ...] when the starting point is one or more changed files that should resolve through declared file bindings. The command resolves seed specs, includes those seeds, then includes active related specs up to the requested relationship depth and item limit. When bindable registry types declare bindings, --include-bindings exposes metadata for external artifacts such as implementation and test files. Binding metadata is separate from artifact content; this first slice reports that file contents are not included.

    Build focused LLM context from the CLIModel bindings as opt-in type capabilitiesSearch project memory from the CLI
  3. 3

    CLI workflow section

    Defines the README section that summarizes the CLI workflow capabilities from command-owning decisions.

    Generate Graphviz relationship graphsSearch project memory from the CLIBuild focused LLM context from the CLIList registry types and specs from the CLI
  4. 4

    Common commands section

    Defines the README command table for common Grounded CLI workflows.

    Generate Graphviz relationship graphsSearch project memory from the CLIBuild focused LLM context from the CLIModel bindings as opt-in type capabilitiesList registry types and specs from the CLI
docs/drift-checks.md
  1. 1

    Drift guardrails section

    Defines the drift checks guide section that lists the main validation, audit, and verification guardrails.

    Generated view is staleRequired canonical fact lacks declared test coverageUnknown referenceUnknown artifact referenceMissing required fieldsVerification command failed
  2. 2

    Common commands section

    Defines the README command table for common Grounded CLI workflows.

    Generate Graphviz relationship graphsSearch project memory from the CLIBuild focused LLM context from the CLIModel bindings as opt-in type capabilitiesList registry types and specs from the CLI
docs/PUBLISHING.md
  1. 1

    GitHub Pages publishing section

    The GitHub Pages deployment workflow builds the root generated Grounded docs at the Pages site root and the Todo example site under todo/, then publishes them from an assembled Pages artifact. Rendered site directories remain ignored by git.

    Prepare documentation site for GitHub Pages
  2. 2

    Release publishing section

    Defines the publishing guide section that summarizes publishing and generated documentation release decisions.

    Prepare documentation site for GitHub PagesRelease publishing and documentation styling as 0.8.0Release graph presentation and sidebar accordions as 0.9.0Prepare PyPI package publishingRelease PyPI-ready Grounded as 1.0.0Release focused context CLI as 1.1.0Release changed-file context lookup as 1.2.0Release suffix collection field type links as 1.2.1
skills/audit-grounded-knowledge-graph/SKILL.md