Skip to content

FE-692: Planning groundwork#91

Merged
TimDiekmann merged 7 commits into
mainfrom
ln/fe-692-planning-groundwork
May 7, 2026
Merged

FE-692: Planning groundwork#91
TimDiekmann merged 7 commits into
mainfrom
ln/fe-692-planning-groundwork

Conversation

@lunelson
Copy link
Copy Markdown
Contributor

@lunelson lunelson commented May 5, 2026

Reconciles intent-spec planning groundwork on top of FE-691's multi-chat substrate, making MULTI_CHAT the concrete phase-one design and leaving PATCH_LEDGER as deeper future semantic mutation guidance.

Updates MULTI_CHAT to use reconciliation_need, a softer dual-pointer migration, primary_chat_id / chat.active_turn_id, caused_by_turn_id plus nullable caused_by_patch_id, and to supersede older side-chat substrate assumptions.

Syncs canonical SPEC/PLAN with non-colliding IDs: Requirement 39, A79-A80, D138, and I111; PLAN now treats multi-chat substrate + reconciliation needs as the active frontier, with continuous workspace next.

Keeps INTENT_SPEC_EVOLUTION and archived REVISIT references linked to MULTI_CHAT/PATCH_LEDGER so revisit/cascade, edge semantics, and future patch ledger point at the correct design layer.

Verification: npm run verify.

@linear-code
Copy link
Copy Markdown

linear-code Bot commented May 5, 2026

Copy link
Copy Markdown
Contributor Author

lunelson commented May 5, 2026

@lunelson lunelson changed the title first pass on intent spec concepts + current db diagram FE-692: Planning groundwork May 5, 2026
@lunelson lunelson marked this pull request as ready for review May 5, 2026 16:25
@cursor
Copy link
Copy Markdown

cursor Bot commented May 5, 2026

PR Summary

Low Risk
Documentation-only changes that reframe the planning/design frontier; no runtime or schema changes are introduced, so risk is limited to potential reviewer confusion if guidance is misinterpreted.

Overview
Updates the project’s planning/design documentation to make MULTI_CHAT.md the concrete Phase 1 proposal (chat containers + reconciliation_need) and position PATCH_LEDGER.md as the longer-term semantic mutation/changeset follow-on.

Rewrites memory/PLAN.md to treat the multi-chat substrate + reconciliation queue as the active infrastructure frontier (with continuous workspace next) and reshapes the horizon items around intent-spec ontology, edge semantics policy, and a future patch ledger.

Archives older design notes (REVISIT_MODULE, WORKFLOW_OWNERSHIP) with clearer “historical-only” disclaimers, adds docs/design/README.md to formalize canonical-vs-design-doc guidance, and appends the associated plan-history sync entry.

Reviewed by Cursor Bugbot for commit 43af44d. Bugbot is set up for automated code reviews on this repo. Configure here.

@lunelson lunelson requested a review from kostandinang May 5, 2026 16:26
@augmentcode
Copy link
Copy Markdown

augmentcode Bot commented May 5, 2026

🤖 Augment PR Summary

Summary: This PR reconciles and promotes recent intent-spec / patch-ledger design groundwork into canonical project memory, while archiving superseded design notes.

Changes:

  • Updates memory/PLAN.md to narrow the active frontier to continuous workspace, and captures new horizon work around intent graphs, reconciliation, chat containers, and semantic changesets/patches.
  • Updates memory/SPEC.md to explicitly shift direction from planning specs toward intent specs, adds Requirement 38, and records new assumptions/decisions on progressive checkability, invariants/examples, reconciliation needs, and patch history.
  • Adds new design docs: docs/design/INTENT_SPEC_EVOLUTION.md (raw synthesis) and docs/design/PATCH_LEDGER.md (working proposal), plus docs/design/README.md boundary guidance.
  • Archives superseded design notes under docs/archive/design/ and updates cross-doc links accordingly.
  • Adds DB schema diagram artifacts (docs/design/schema.dbml / schema.dbdiagram) as supporting design/reference material.

Technical Notes: Documentation-only change set; PR description indicates verification via npm run verify. Be mindful of keeping schema reference artifacts from diverging over time.

🤖 Was this summary useful? React with 👍 or 👎

Copy link
Copy Markdown

@augmentcode augmentcode Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. 2 suggestions posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

Comment thread memory/PLAN.md
Comment thread docs/design/schema.dbml Outdated
@lunelson lunelson self-assigned this May 6, 2026
@lunelson lunelson changed the base branch from main to graphite-base/91 May 6, 2026 13:42
@lunelson lunelson force-pushed the ln/fe-692-planning-groundwork branch from f47d917 to 2952265 Compare May 6, 2026 13:42
@lunelson lunelson changed the base branch from graphite-base/91 to ka/fe-691-multi-chat-substrate May 6, 2026 13:42
@kostandinang kostandinang changed the base branch from ka/fe-691-multi-chat-substrate to graphite-base/91 May 6, 2026 13:50
Copy link
Copy Markdown
Contributor

@kostandinang kostandinang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Three follow-ups against the reconcile, 2 questions on meeting outcomes, one copy-edit.

Comment thread docs/design/MULTI_CHAT.md
Comment thread docs/design/MULTI_CHAT.md
Comment thread docs/design/MULTI_CHAT.md Outdated
@lunelson lunelson requested a review from kostandinang May 6, 2026 15:08
kostandinang
kostandinang previously approved these changes May 6, 2026
Copy link
Copy Markdown
Contributor Author

lunelson commented May 6, 2026

Merge activity

@lunelson lunelson force-pushed the ln/fe-692-planning-groundwork branch from 9f3f4ec to 64f073e Compare May 7, 2026 10:44
@lunelson lunelson force-pushed the graphite-base/91 branch from 40f7926 to 33db9aa Compare May 7, 2026 10:44
@lunelson lunelson changed the base branch from graphite-base/91 to ka/fe-691-multi-chat-substrate May 7, 2026 10:44
@github-actions github-actions Bot dismissed kostandinang’s stale review May 7, 2026 10:44

Latest approval commit 9f3f4ec is not an ancestor of 64f073e, indicating rewritten history after approval

@lunelson lunelson requested a review from kostandinang May 7, 2026 10:46
kostandinang
kostandinang previously approved these changes May 7, 2026
@kostandinang kostandinang changed the base branch from ka/fe-691-multi-chat-substrate to graphite-base/91 May 7, 2026 11:06
@lunelson lunelson force-pushed the graphite-base/91 branch from 33db9aa to 817e0c3 Compare May 7, 2026 12:12
@lunelson lunelson force-pushed the ln/fe-692-planning-groundwork branch from 64f073e to 43af44d Compare May 7, 2026 12:12
@lunelson lunelson changed the base branch from graphite-base/91 to main May 7, 2026 12:12
@github-actions github-actions Bot dismissed kostandinang’s stale review May 7, 2026 12:13

Latest approval commit 64f073e is not an ancestor of 43af44d, indicating rewritten history after approval

@TimDiekmann TimDiekmann added this pull request to the merge queue May 7, 2026
Merged via the queue into main with commit 5187f17 May 7, 2026
12 checks passed
@TimDiekmann TimDiekmann deleted the ln/fe-692-planning-groundwork branch May 7, 2026 12:22
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.

3 participants