doc: readme words

Author: davidlee

README.md

@@ -223,7 +223,6 @@ Boot up, install, and ask the agent to show you around.
 
 |Feature|Blurb|
 |---|---|
-|**Multi-Language Spec Sync**|Automatically sync specifications with Go, Python & TypeScript/JS codebases|
 |**Architecture Decision Records (ADRs)**|Record, find, manage and track architectural decisions|
 |**Product Specs**|Product requirement docs, with customer-focused value drivers, use cases and personas|
 |**Tech Specs**| Start with architectural vision - or fill it in after the fact, scaffolded by deterministically generated documentation|
@@ -232,10 +231,10 @@ Boot up, install, and ask the agent to show you around.
 |**Delta/Change Tracking**|Create a delta to implement a set of requirements or backlog items, deltas, implementation plans and revisions. Record structured data (entry / exit criteria; files and commits) through planning and implementation. Record verification evidence (automated tests, agent or human review), driving requirement status updates.|
 |**Backlog Management**|Tooling to create, search & filter Issues, Risks, Problem Statements, Improvements and related artefacts. Prioritise your backlog - just by moving lines up & down in your $EDITOR.|
 |**Documentation Generation**|Compact, legible, deterministic markdown documentation from code. Autogenerated spec stubs for new code; change tracking.|
+| **Relational Artifacts**  | Documents are linked with rich semantics supported by CLI validation, search and management tools. |
 |**Metadata Schema Validation**|Ensure consistency across specification artifacts. CLI tooling support for agents: schema documentation and validation.|
 |**Customisable Templates & Agent Commands**|Optionally install templates & commands locally to customise your workflow; fallback to defaults.|
-|**Orphaned Spec Detection**|Identify & safely remove tech specs for deleted source files.|
-|**Audits**|Record agent (or human) research & inspection to verify implementation, feeding back into requirements & spec status.|
+|**Audits & Drift Ledgers**|Record agent (or human) research & inspection to verify implementation, feeding back into requirements & spec status. If you need to manage ambitious programs of work and maintain canonical truth in the face of LLM vomit, there are tools to help. |
 |**Spec Revisions**|Optionally contextualize changes to product/architectural specs, with data as structured as makes sense. Start your changes with a revision to capture the design changes - or end with one to represent your findings and what actually happened.|
 |**Markdown + Git**|Why use a shitty Saas when version controlled text is this powerful, and agents can work with it so fluently? I'm sure you can pipe it into other, lesser tools if you need it.|
 |**Zero Lock-In, Zero Cost**|Things change fast, but if text in open formats goes out of fashion, all bets are off.|