| name | ingest |
| description | Ingest an explicitly selected source into the local project wiki with provenance, secret checks, entity links, and an append-only change record. |
Wiki Ingest
Run this workflow directly in the current conversation. It is a knowledge-maintenance
workflow, not feature planning.
Workflow
- Resolve exactly one source. Accept one user-supplied local file or URL. Reject
directories, globs, credential/environment files, device paths, and paths outside
the workspace. For a URL, fetch only that URL and record the final URL.
- Prepare safely. Ensure
ai_context/sources/ and ai_context/wiki/ exist. Before
storing raw content, verify the destination is ignored using
git check-ignore --no-index; if it is not ignored, stop without copying.
- Fingerprint and deduplicate. Before arming the shell guard, compute SHA-256 over
the explicitly authorized source bytes. If the wiki log
already records the same hash, report the existing pages and do not rewrite them.
- Store raw input immutably. Copy to a sanitized deterministic name under
ai_context/sources/; never overwrite a different file. Keep raw content out of the
response and out of version control.
- Arm the guard. Create
ai_context/.spk-wiki-build immediately before extracting
from the stored source or writing wiki content. While it is active, use only
non-shell read/search/write tools; shell execution is fail-closed except for an
exact marker-cleanup command. Remove the marker in a finally-style cleanup on every
success, failure, cancellation, or blocked return.
- Extract conservatively. Read the wiki schema. Create or update only notable
concept, entity, decision, plan, or learning pages. Every non-obvious claim
needs a source citation. Redact secret-shaped values as
<REDACTED:type origin=sources/file:line>; never copy the value.
- Link and verify. Maintain frontmatter, internal links/backlinks, and
index.md. Use non-shell reads/searches to run secret, link, schema, and orphan
checks over the proposed wiki diff before writing. Fail closed on secret-scan
errors.
- Record evidence. Append one log entry with UTC timestamp, source path/URL,
content hash, pages created/updated, redaction count, and verification result.
- Cleanup and report. Remove the guard and return a typed evidence receipt with
source hash, wiki paths, verification, risks, and any skipped claims.
Do not delegate to a feature-planning role. A read-only helper may summarize a very
large source, but the main conversation owns path validation, writes, verification,
and cleanup.
Evidence Receipt
Return spk.evidence/v1 with status, source hash, created/updated artifacts,
verification commands/results, redaction count, risks, and next action.
Guardrails
ai_context/sources/ is private raw input; ai_context/wiki/ must remain commit-safe.- Never ingest more than the explicitly supplied source.
- Never overwrite user-authored wiki content without merging and preserving intent.
- No guard file may remain after the workflow exits.
