# ADR 006: Knowledge graph context with bounded authority

- HTML version: https://robbiepalmer.me/projects/agent-first-writing/adrs/006-knowledge-graph-context-with-bounded-authority
- Project: Agent-first Writing Editor (https://robbiepalmer.me/projects/agent-first-writing.md)
- Status: Proposed
- Date: 2026-09-04
- Initiatives: Semi-autonomous Software Development (https://robbiepalmer.me/initiatives/semi-autonomous-software-development.md)

# Context

Generic writing tools see the draft but not the project's source decisions.
They cannot reliably tell which architecture decision supports a claim, which
terms the author uses elsewhere, or which evidence may be stale.

The Personal Site knowledge graph already connects projects, architecture
decisions, technologies, and public artifacts. That context can improve editing,
but retrieval does not grant authority to decide facts or publish in the
author's name.

# Decision

Use the knowledge graph to supply editorial context. The editor may retrieve the
project a draft describes, linked architecture decisions, established
terminology, and claims that need fresh evidence.

Return proposed public artifacts and structured edit history to the graph. Do
not let the editor decide what is true, replace research or fact checking, or
publish under a person's name without explicit authority and final review.

# Consequences

Suggestions can cite the project's own decisions and preserve local terms
instead of applying generic style blindly. The structured edit history can also
improve later evaluation.

Graph context can contain gaps or stale claims. The editor must present retrieved
material as context, keep factual verification separate, and fail safely when
the graph contains no source decision.

---

Markdown index of this site: https://robbiepalmer.me/llms.txt