okf-wiki-ingest

Ingest a source

Treat wiki/ as the OKF bundle. Read wiki/index.md, wiki/log.md, and all relevant files under wiki/governance/ before writing.

Workflow

1. Identify the captured source ID in sources/manifest.json, then inspect its processing state:

   python3 scripts/ingest_source.py status --vault <path> --source-id <id>
   

1. Read the immutable source completely, its attachments, existing related concepts, wiki/index.md, and relevant governance. Never alter the captured source.

2. Present three to five durable takeaways and wait for explicit operator approval. Do not create a proposal or modify the wiki before approval.

3. Build a JSON proposal with source_id, the approved takeaways, and pages containing path, title, and complete Markdown content. Follow references/concept-template.md: use OKF v0.2 generated, structured sources, optional verified/status, and footnotes whose labels match sources[].id. The proposed wiki/sources/ page must declare captured_source_id equal to the manifest source ID.

4. Prefer existing concept paths. For a new source that updates an existing concept, list that path in proposal update_paths. If status reports update, include every previously associated page and preserve each # Human Notes section verbatim. Never create a parallel concept to avoid updating the existing one.

5. Apply only after the same takeaways were approved:

   python3 scripts/ingest_source.py apply --vault <path> \
     --proposal <proposal.json> --approve-takeaways
   # For a previously processed source:
   python3 scripts/ingest_source.py apply --vault <path> \
     --proposal <proposal.json> --approve-takeaways --update
   

6. The helper rejects unapproved writes and unsafe re-ingestion, preserves Human Notes, updates wiki/index.md, the dated sections in wiki/log.md, and wiki/ingest-state.json, then runs its vendored lint validator against a staged candidate. It journals multi-file writes and restores an interrupted commit on the next status or apply command. Report its result and run the full lint skill for qualitative checks. Do not commit vault changes.

Selection rules

• Extract only distinct, durable concepts. Select type from wiki/governance/taxonomy.md; govern an extension before using it.
• Use relative Markdown links and the governed relation vocabulary.
• Preserve contradictions as sourced positions; never silently reconcile them.
• Read policy before assigning origin, sensitivity, confidence, or a profile.