Ingestion redesigned: harvest from the estate, not just content/

- docs/phase-4-corpus.md rewritten: Gitea (all repos), vault via Gitea, Graphify
  graph, curated content as tier 1. Platform guides are config and public copy.
- docs/phase-5-ai-overlay.md: citations to originals, tier preference, live
  source readout.
- Board: AUD-144 (index content/ only) retired; AUD-147 replaces it, blocked by
  AUD-141 and AUD-142. AUD-145 relinked to AUD-143 and AUD-147.
This commit is contained in:
Sam Rolfe
2026-10-26 22:16:33 +11:00
parent 9fae1c7dd8
commit 5c0622c1b1
2 changed files with 165 additions and 49 deletions

View File

@@ -80,3 +80,43 @@ One hand-written TypeScript island, ES modules, no framework, no bundler.
| Panel refactor needed | Phase 2 §2.4 contract; if it fails, fix the panel contract, do not fork the UI |
| Streaming stalls behind Caddy | Explicit flush settings; p90 measurement, not a spot check |
| Answers drift from the site | Citation verification is a node, not a hope |
---
## 5.6 Citations point at the original
An answer cites where it came from, not a curated page standing in for it.
| Source | Cited as |
|---|---|
| Gitea repo file | full URL to the file in Gitea |
| Vault note | full URL to the note in `sam/obsidian-vault` |
| Graph answer | the note title the node came from, plus its URL |
| Curated claim | the site page |
A citation whose URL cannot be opened is dropped, not rendered. A claim with no
traceable origin is not returned at all.
## 5.7 Curated outranks harvested
`content/` is tier 1; everything harvested is tier 2. When the two disagree, the
tier 1 claim wins and the answer says so plainly: the curated description is
current; the older text is background.
This is the rule that stops a stale README from quietly overwriting Sam's own
description of his work.
## 5.8 The live source readout
While the answer streams, a panel shows what is being read, named as the visitor
would recognise it:
```
reading · gitea/photo-pipeline/README.md
· obsidian/210 AI Resume/Graphify.md
· graph · community 42 · vault infrastructure
```
This is a feature, not a debug view. It answers the question every recruiter has
and does not ask: is this making things up? Show the working — it is also the most
convincing demonstration of the system on the page.