This hub gathers the plumbing by which raw activity becomes queryable knowledge. On the execution side, the [webhook-mode attribution filter] (Claim_SubworkflowAttributionFilter) (Jan 17) draws the line between top-level proxy-dispatched tool calls and sub-workflow calls that must not be double-counted. The same week, [hand-correlating three data sources] (Narrative_ManualCorrelationAuditGap) for the enterprise customer metrics exposed a structural gap in the audit schema — surfacing a proposed outcome_summary JSONB column. On the knowledge side, [narrative extraction into RDF] (Obs_NarrativeOntologyExtraction) feeds a graph, and an [annotate function] (Observation_AnnotationQuote) maps AI claims back to collective memory like citations. [Personal-graph federation] (Narrative_PersonalGraphFederation) extends the flow outward — a personal repo acting as both filter and expander against the org repo, with an open introspection question. An [HTML-deliverables pattern] (Observation_HTMLDeliverables) sits at the client-facing edge. Together these span ingestion, attribution, audit, extraction, and federation — but they are stages spread across domains, not a single resolved pipeline.
Witness phrases
verbatim Filter n8n executions to mode=webhook for top-level proxy-dispatched tool calls.
verbatim Adding an outcome_summary JSONB column at audit-write time would collapse two days of investigation into a single SQL query.
verbatim correlating three data sources by hand (n8n executions API, proxy Docker auth log, n8n execution detail)
verbatim does introspect take a vector of [& [owner repo]]?
verbatim analogous to research paper citations
verbatim Audit-gap child is a critique, not a flow: manual correlation revealed the schema lacks per-call outcome metrics, proposing a write-time fix rather than describing current behavior.
verbatim Personal-graph federation carries an unresolved design question (does introspect take an [owner repo] vector?) — direction, not a settled mechanism.
verbatim HTML deliverables is a domain outlier — client-facing output delivery, not internal data plumbing like the n8n/audit/extraction children.
verbatim Two distinct registers coexist: low-level execution/audit instrumentation (n8n, Docker logs) vs. knowledge-graph semantics (RDF extraction, annotation-as-citation, federation).
In this area
NarrativeNarrative_PersonalGraphFederation Personal graphs federated with org repos act as both filter and expander on worldview changes
ObservationObs_NarrativeOntologyExtraction Scarlet's tool extracts narratives from raw transcripts into an RDF knowledge graph using a narrative architecture ontology.
4 further nodes are not published in the public projection. Each node links from the entity index.