This is the home of the complete Holistic Code Specification (HCS) reference documentation aimed at interpretation roles.
These documents provide all the information needed to understand and interpret HCS files — the structured-English, evidence-linked, pattern-compressed system blueprints generated from source code.
| Document | Purpose |
|---|---|
| Overview of HCS | What HCS is, its purpose, core concepts, and holistic dimensions |
| Language Reference | Grammar, syntax, keywords, casing rules, and statement schemas |
| Intermediate Model | Machine-facing data model, types, and evidence structures |
| HCS Fact Types | Complete taxonomy of fact types captured from source code |
| HCS Patterns | Pattern system, type system, expansion templates, and standard library |
| Changelog | Version history and release notes |
For comprehensive understanding:
- Start with Overview of HCS to understand what HCS is and why it exists
- Read Language Reference to understand the DSL syntax
- Study Intermediate Model to understand the underlying data structures
- Reference HCS Fact Types for the evidence taxonomy
- Consult HCS Patterns for pattern compression and expansion
HCS is a specification artifact with:
- Structured English statements
- Typed semantics (every statement maps to a machine-checked schema)
- Traceability (every claim links back to evidence in code)
- Pattern compression (common idioms collapse into named patterns)
A system is reproducible from HCS when it contains enough detail to regenerate:
- Domain behaviour (use-cases and workflows)
- Interface contracts (UI + APIs + message schemas)
- Data structures (entities, constraints, relationships)
- Security posture (auth flows, authorization rules, boundaries)
- Integration behaviour (calls, retries, timeouts, idempotency)
© 2026 Vibgrate. All rights reserved. | License | vibgrate.com