Skip to content

docs(specs): Implementation priorities plan from .specs review#328

Draft
glassBead-tc wants to merge 1 commit into
mainfrom
cursor/specs-implementation-priorities-afac
Draft

docs(specs): Implementation priorities plan from .specs review#328
glassBead-tc wants to merge 1 commit into
mainfrom
cursor/specs-implementation-priorities-afac

Conversation

@glassBead-tc

Copy link
Copy Markdown
Member

Summary

Adds .specs/IMPLEMENTATION-PRIORITIES-PLAN.md — a planning artifact that reviews the spec corpus and proposes six sequenced implementation initiatives with explicit reasoning, dependency map, branch naming, and deferrals.

What’s in the plan

  1. SPEC-SRC-006 — MCP root session recovery (data-loss fix; load_context without remembered session IDs)
  2. SPEC-CHX-001 — Cognitive harness quick wins (tb.t(), recall primitives, docs for auto-numbering)
  3. SPEC-GW-011 — First-call-only gateway schemas + thoughtbox_operations tool
  4. OODA loops MCPIMPLEMENTATION-READY embedding + .claude/thoughtbox/ analytics
  5. ADR-022 peer notebooks — Web inspection + manifest lifecycle before smolvm
  6. SPEC-EVAL-001 — Wire LangSmith fitness back into DGM (partial code exists)

Also documents secondary queue and explicit non-goals (full Canonical IR/TBX-C1, smolvm before inspection, etc.).

Method

Cross-read spec index, handoffs, and spot-checked src/ for shipped vs. draft-only (e.g. no embed-loops, no sessionSchemasSeen, Part 1 peer notebook merged without web peers routes).

Type

Documentation only — no runtime behavior change.

Open in Web Open in Cursor 

Synthesizes highest-value specs into six sequenced initiatives with
reasoning, dependency map, and explicit deferrals. Cross-checks against
current src/ implementation status.

Co-authored-by: glassBead <glassBead-tc@proton.me>
@vercel

vercel Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
thoughtbox-web-two Ready Ready Preview, Comment Jun 3, 2026 5:17am

@supabase

supabase Bot commented Jun 3, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project akjccuoncxlvrrtkvtno because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants