Skip to content

Map: post-review improvements (2026-10-23) #18

Open

Description

@IadityaM

Destination

Every recommendation accepted on 2026-10-23 carried to a build-ready decision, not code: T-01, T-04 and T-06 specified for /spec build sessions; D-04, D-06, D-07 and the seven owner-call tickets of D-09 each decided or ruled out. Builds happen in their own sessions, behind the owner's commit gate.

Notes

  • Repo: factstack (this repo). main @ 0dfebf6 is production (Pages deployment 551fb85e, rollback 43291212).
  • Sources (local, git-ignored .ag/ of the main checkout; cite paths, they are not linkable): .ag/tickets/2026-10-23-openlore-improvements.md (T-01…T-10, acceptance criteria, skeptics' evidence), .ag/research/2026-10-23-openlore-comparison.md and -review-result.json, .ag/decisions.md (D-04, D-06, D-07, D-09), .ag/findings.md (F-103…F-115), .ag/audits/2026-10-22-fix-the-issues.html. gbrain pages: factstack-vs-openlore-2026-10-23, factstack-openlore-tickets-2026-10-23.
  • Skills every session consults: grilling and domain-modeling; research for AFK tickets; a resolved build-ready decision is handed to /spec, never built here.
  • Settled, never re-litigated: the owner's commit/deploy gate (literal "commit" / "deploy" only); the R5 claims policy (no unmeasured numbers on public surfaces); no hosted knowledge server (compose with OpenLore); chrome-ext parked; every secret flagged with its path, fixtures not graded; transcript reading opt-in.
  • Execution override (owner, 2026-10-23): AFK task tickets are allowed only for reversible chores behind the full 18-step battery (the babel 8 / chokidar 6 bump); the CVE-job secrets are a HITL task for the owner.
  • Cross-map blocking: two tickets wait on the FACTS-for-Agents map (Map: FACTS-for-Agents spec (phases 0–1) #5): Team mode waits on Pack commit policy (Pack commit policy #7); Public install wording waits on Publish or fallback-only (Publish or fallback-only #8).
  • Conventions: tickets are children by "Part of #"; blocking is a "Blocked by:" line naming the tickets; research findings are posted as resolution comments.

Decisions so far

  • Streamable HTTP in the MCP SDK: SDK 1.32.1 ships StreamableHTTPServerTransport + createMcpExpressApp (Host-only guard; add the Origin check from ui-server); one Server per session; bearer via requireBearerAuth; Claude Code and Codex send static headers; no idle expiry in the SDK.
  • MCP clientInfo for attribution: Server.getClientVersion() returns the handshake clientInfo (no clientInfo in tool-handler extra); Claude Code sends claude-code, Codex codex-mcp-client, Cursor cursor-vscode (2025, unverified); precedence FACTS_AGENT env > normalized clientInfo.name > free-text agent arg.
  • TypeScript 7 readiness: TypeScript 7.0.2 is GA and this config is 7-clean (no removed options in use), but typescript-eslint needs TS 6 via the @typescript/typescript6 alias until 7.1 (stable planned 2026-11-24); adopt on a branch with the two-package layout, delete tsbuildinfo, vitest >= 5.0.5.

Not yet specified

  • The team-tier shape (hosted or not, who pays) that the localhost HTTP mode, the docset recipe and any served pack ultimately hinge on; sharpen once T-02/T-03 resolve.
  • How MEMORY.md renders pending versus accepted learnings and how a human accepts one from the dashboard; sharpen after Learnings log bounds resolves.
  • Whether the first-paint and lazy-chunk budgets become hard caps (today reported only); revisit after the usage counters exist.

Out of scope

  • A hosted knowledge server or identity-scoped served pack (compose with OpenLore instead; D-09).
  • MCPB packaging and non-loopback remote MCP clients (wait for MCP_PUBLISHED; the server sits on the checkout).
  • A generic grep/shell MCP tool; folder rules, publish inbox, content-hash provenance; configurable MEMORY.md caps (review: nothing to govern yet).
  • The FACTS-for-Agents spec items (map Map: FACTS-for-Agents spec (phases 0–1) #5) and the facts-pack wire grammar (F-26 goes to facts-pack research/ first).
  • The browser producer / web-app composition; the Chrome extension.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions