grace-ontologylisted

The GRACE annotation vocabulary — what MODULE_CONTRACT, FUNCTION_CONTRACT, BLOCK, LOG_ANCHOR and knowledge-graph tags mean, how code and architecture tiers relate, and how product intent is linked without embedding a product methodology. Read before writing or reviewing GRACE markup or extending the knowledge graph.
createusernam/setup_project · ★ 0 · AI & Automation · score 65

Install: claude install-skill createusernam/setup_project

# GRACE Ontology — Portable Markup Vocabulary GRACE is used here as a structured transfer format for code and architecture. It records purpose, boundaries, dependencies, flows and verification links so another person or agent can navigate the system without reconstructing those relationships from scratch. GRACE does not define the project's product strategy, business ontology, or architecture method. Those choices remain in `product_brief.md`, `contract.json`, ADRs and the user's design process. ## Enforcement `setup-grace-lint` checks the code-level vocabulary. The `--profile autonomous` profile requires the stricter function contracts and block-anchored logs. `/code-review-expert` and `/build-loop` consume the same checked structure; `/scaffold` creates it before implementation. ## Tier 1: code-level vocabulary | Concept | Markup | Required meaning | |---|---|---| | `MODULE` | file path/name | stable code unit identity | | `MODULE_CONTRACT` | `START_MODULE_CONTRACT` | purpose, scope, dependencies | | `FUNCTION_CONTRACT` | `START_CONTRACT: fnName` | purpose, inputs, outputs, side effects | | `BLOCK` | `START_BLOCK_NAME` / `END_BLOCK_NAME` | named logical region, unique in the file | | `LOG_ANCHOR` | structured log statement | module, function, block and correlation identifier | Relations: - a module has one module contract; - a module contains zero or more named blocks; - declared dependencies point to other modules or external systems; - an exported function has a f