SPIKE: menke-5 guide ingest for agent-context store (SPIKE-001 T01)#24
Draft
jmjava wants to merge 14 commits into
Draft
SPIKE: menke-5 guide ingest for agent-context store (SPIKE-001 T01)#24jmjava wants to merge 14 commits into
jmjava wants to merge 14 commits into
Conversation
Add exploration branch artifacts for SPIKE-001 T01 — append-ingesting orchestrator agent-context and spdd into the existing Guide/Neo4j corpus (leg 2 RAG chunks) using the ingest-to-hub branch's git incremental ingest. - menke-5 profile template pointing at memory, canvas, and analysis dirs - append-orchestrator-context.sh helper and operator runbook - exploration log template for MCP spot-checks after ingest - SPIKE-001 canvas and guide-rag docs updated with menke-5 references Co-authored-by: John Menke <jmjava@gmail.com>
- Add canonical analysis artifact with branch isolation, experiment design, and mock fixture plan (T07) - Create agent-context/features/SPIKE-001 workspace (requirement, analysis context, progress log, canvas pointer) - Update canvas with T07/T08, safeguards for staying off main until T06 - Link operator runbook and exploration log to SPDD analysis chain - Register Work ID on spike branch in work-registry.tsv Co-authored-by: John Menke <jmjava@gmail.com>
Co-authored-by: John Menke <jmjava@gmail.com>
- Add examples/retrieval-fixture mock project (SPIKE-FIX-001) with seeded indexes - Gold test: tests/test-retrieval-fixture-resolver.sh (15 assertions, 3 cases) - Fixtures: spike-001-retrieval-gold.tsv, spike-001-mcp-queries.tsv - menke-fixture Guide profile + append-retrieval-fixture.sh for mode B - CI: test-retrieval-fixture-resolver workflow - Update canvas T07, progress log, TESTING.md Co-authored-by: John Menke <jmjava@gmail.com>
- Add retrieval A/B ledger stub and mode (a) baseline capture - run-retrieval-ab-fixture.sh: --capture-a, --check-mcp, expect match/no_match - verify-spike-guide-setup.sh for local Guide prereq checks - Commit generated spike-001-mode-a-baseline.tsv (3 fixture cases) - CI: test-retrieval-ab-baseline.sh smoke in retrieval fixture workflow Co-authored-by: John Menke <jmjava@gmail.com>
Document leg 2 RAG vs leg 3 structured markdown projection (not DICE proposition pipeline). Add project-spdd-entities.sh, extend verify script for spdd-projection API, update canvas T03 and operator runbook. Co-authored-by: John Menke <jmjava@gmail.com>
Co-authored-by: John Menke <jmjava@gmail.com>
Leg 3 exercised end-to-end: 9 WorkId / 9 Canvas / 12 Area / 21 typed relationships projected, WorkId subgraph read verified over HTTP, and MCP spot-checks recorded showing embedding-only auditability gaps vs typed-edge domain reads. Also documents guide branch build friction (snapshot drift, drivine bump, ONNX native crash during ingest). Co-authored-by: Cursor <cursoragent@cursor.com>
- docs/dice-projection-runbook.md: shareable e2e runbook for running the orchestrator against jmjava/guide cursor/spike-spdd-dice-projection-17f4 - Schema contract: decision/pitfall/pattern + about edges, /area cross-run retrieval, hardening notes, design verification table - Canvas T04: spdd_* MCP tools verified via JSON-RPC Co-authored-by: Cursor <cursoragent@cursor.com>
…acks Not every install has Guide + Neo4j, so DICE is never assumed: new resolve-context-backend.sh probes opt-in marker (agent-context/harness/ guide-dice.md) then endpoint liveness, reporting CONTEXT_BACKEND=guide-dice or files (files is a valid answer, never an error). Command templates in all three adapter packs gain a runtime-gated Context Backend section mapping guide-dice to the spdd_* MCP tools; retro/sync re-project on the persist side. init-project.sh --with-guide opts installs in; grounding rules updated; orchestrator repo dogfoods its own .cursor command pack. Co-authored-by: Cursor <cursoragent@cursor.com>
…internal docgen workflows (check-docgen-dev-boundary, docgen-lint) removed per owner decision - no docgen actions in this repo. SPIKE-FIX-001 fixture canvas gains the Review Checklist / Sync Notes / Final Status sections validate-canvas requires. spike-guide-ingest-agent-context.md marked orchestrator-only so the local-only operator doc stops shipping into target installs. Co-authored-by: Cursor <cursoragent@cursor.com>
…statuses docs/guide-flow.md explains the Guide flow end to end: dual ingest (chunks vs typed entities), runtime backend resolution, per-phase spdd_* usage, and the cross-run persist loop. README leads with a Current Work section pointing at it. Canvas T01/T03/T04/T08 marked complete to match delivered state. Co-authored-by: Cursor <cursoragent@cursor.com>
menke-fixture must clear content.versioned.versions/supplementary — urls: [] is ignored (urls is computed), so FORCE_STARTUP_INGEST was re-embedding the whole Embabel docs corpus. Append script now regenerates the profile with absolute paths and refuses non-empty versions. Mode (b) MCP queries verified live (billing/canvas/pitfalls hits; payments negative control). Co-authored-by: Cursor <cursoragent@cursor.com>
Owner
Author
Sync / test status — 2026-07-11Branch tip What was verified
Remaining
Guide PR: jmjava/guide#2 |
…pike branch Point the primary flow doc at the spike-branch blob URL so readers on main still reach the WIP guide-flow write-up. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Jul 15, 2026
4 tasks
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.
SPIKE-001 — Guide as optional DICE context backend
Status: Draft — do not merge until T06 go/no-go.
This PR (orchestrator)
resolve-context-backend.sh+ optionalagent-context/harness/guide-dice.md(init-project.sh --with-guide); slash commands augment withspdd_*only when liveexamples/retrieval-fixture/+ resolver gold test (CI)docs/guide-flow.md,docs/dice-projection-runbook.md, README Current workPaired guide branch (leg 3)
jmjava/guidecursor/spike-spdd-dice-projection-17f49b8fbafNot the DICE proposition pipeline. Leg 3 = structured markdown →
__Entity__via projection API +spdd_*MCP tools.Test status (2026-07-11)
bfa7f68(8 workflows)GET …/work/{workId}CONTEXT_BACKEND=guide-dicewhen Guide up;fileswhen not.cursor/commandsinstallCanvas ops
Complete: T01, T02, T03, T04, T05, T07, T08. Remaining: T06 go/no-go.
Operator flow
See
docs/guide-flow.mdanddocs/dice-projection-runbook.md.