docs(harness): add spatial-vs-temporal context taxonomy#10
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a documentation-only “Context model: spatial vs temporal” taxonomy to the /harness README to give a shared vocabulary for how the harness manages context.
Changes:
- Introduces spatial vs temporal framing and two tables enumerating existing context surfaces/mechanisms.
- Adds a short paragraph situating the PTC loop across the two axes.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Reframe the hooks-on-feedback-axis claim: post-compact-reinject.sh is a hook implementing a context-preservation mechanism, so it stays in the temporal table; sensor hooks remain off both tables. - Add AGENTS.md to the spatial table — referenced in the temporal mechanism (post-compact reinjection) but was missing from spatial.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #7. Adds a "Context model: spatial vs temporal" section to
skills/harness/README.md, naming the two axes the harness already manages and tabling every existing surface against them.What changed
skills/harness/README.md— new section between## Where the idea comes fromand## When to use. Two tables (spatial / temporal) plus a short framing paragraph and a closing paragraph that locates the PTC loop on both axes.SKILL.md,CLAUDE.md.tmpl, or any other file.Why
The harness already manages context on two axes — spatial (CLAUDE.md, MEMORY.md index, loaded skills, system prompt) and temporal (post-compact-reinject, auto-memory,
memoize, snapshot, monthly audit). We didn't name them that way, so design discussions had no shared vocabulary and gaps weren't visible at a glance. Naming the axes is pure docs leverage — no cost, makes future coverage decisions easier.Deviations from issue #7's draft
(gap) memory rot — see #5. harness: memory-consolidate sub-action + scheduled routine (proactive memory hygiene) #5 shipped (memoizesub-action via PR feat(harness): add memoize sub-action for memory hygiene #8) before this work, so the row now reads "filled bymemoize(deterministic) + weekly remote routine (semantic)" instead of being a gap./critique(harness: name the PTC loop + add /critique slash command #6 / PR feat(harness): name the PTC loop and add /critique command #9) is a temporal surface inside a single session — between tool steps. Not in the original draft tables but it belongs there now that the surface exists.Validation
./scripts/harness-check.shpasses (shellcheck, ruff, mypy, pytest).skills/harness/SKILL.mdand the install matrix in the README — every spatial/temporal surface that exists is listed; nothing fabricated.verify-before-stop.shcallout from the closing PTC paragraph (it conflicted with the "hooks aren't context" framing right above it).