2 commits

Author	SHA1	Message	Date
Cyber MacGeddon	245d705171	Updated tech specs for: ... - Tool candidates on Analysis events - Token counts — per-event on provenance, aggregated on service responses, --show-usage on all CLIs - Termination reason on terminal events - Tool error/retry events with Error mixin - Sub-agent linkage (was already correct) - Vocabulary publication (OWL ontology) - Step counter on iteration events - Pattern decision entity in DAG - Latency breakdown (LLM + tool duration) - Envelope field naming unified (message_type) - LLM parse errors handled gracefully	2026-04-13 17:26:08 +01:00
cybermaggedon	64e3f6bd0d	Subgraph provenance (#694) ... Replace per-triple provenance reification with subgraph model Extraction provenance previously created a full reification (statement URI, activity, agent) for every single extracted triple, producing ~13 provenance triples per knowledge triple. Since each chunk is processed by a single LLM call, this was both redundant and semantically inaccurate. Now one subgraph object is created per chunk extraction, with tg:contains linking to each extracted triple. For 20 extractions from a chunk this reduces provenance from ~260 triples to ~33. - Rename tg:reifies -> tg:contains, stmt_uri -> subgraph_uri - Replace triple_provenance_triples() with subgraph_provenance_triples() - Refactor kg-extract-definitions and kg-extract-relationships to generate provenance once per chunk instead of per triple - Add subgraph provenance to kg-extract-ontology and kg-extract-agent (previously had none) - Update CLI tools and tech specs to match Also rename tg-show-document-hierarchy to tg-show-extraction-provenance. Added extra typing for extraction provenance, fixed extraction prov CLI	2026-03-13 11:37:59 +00:00