previews · Architecture & design · Agent Platform milestones

Agent Platform · milestone map

Agent Platform — milestones

The project's milestone map: one requirements explainer per milestone, published here before implementation planning. Each card links its reader-facing explainer and the canonical plan artifact in the repo.

By Adolfo Tamayo Briceno · Lawyer Experience (LEX)

Linear project → Requirements explainers M2 · M3 · M4 Living hub

This hub indexes the requirements explainer for each Agent Platform milestone. The explainer is published before implementation planning so the scope can be reacted to before units and PRs are cut. All three milestones are live — each card below links its explainer and the canonical plan artifact.

M1 · first pass

M1 (framework core + Langfuse observability, PRs #11792–#11801) shipped without a brainstorm — its record is the work plan and LEX-646, not a milestone explainer.

The milestones

M2

Generalise beyond matters

Scope confirmed · pre-planning

Scope-anchored threads, non-matter authorization, VFS write verbs, a firm-scoped matters:// namespace, and Langfuse parity.

Read the explainer → platform-v3/docs/plans/2026-07-03-002-feat-agent-platform-m2-generalise-beyond-matters-plan.md
M3

Full Lawrence 2 on TS

Scope confirmed · pre-planning

Port the production tools from the Python framework, then the static skills — the migration payoff: full Lawrence 2 running on the TS platform.

Read the explainer → platform-v3/docs/plans/2026-07-03-003-feat-agent-platform-m3-full-lawrence2-on-ts-plan.md
M4

Background and durable execution

Scope confirmed · pre-planning

Event-triggered, user-less, durable agent runs on the TS framework, plus a generic proposal review primitive that makes their output actionable — with all egress hard-gated behind human approval.

Read the explainer → platform-v3/docs/plans/2026-07-03-001-feat-agent-platform-m4-background-execution-plan.md

Proposed ticket map

proposal · 2026-07-05 · not yet in Linear

Derived from the three milestone requirement plans. Existing tickets are drawn solid, proposed ones dashed, and Pratik's in-flight durable-streams stack as an external dependency: a chance to react to the shape before these are minted into Linear.

existing (LEX-id) proposed external dependency depends on sequencing open

Edge notes. ds → lex641 lands first · lex641 ⇢ lex642 session attribution · lex641 → cut thread persistence · ds ⇢ runs merge order open · runs ⇢ codeexec later. Dashed edges (⇢) mark sequencing that is still open.

What’s being proposed

M2 +1 ticket

  • Matter-intake proving agent

M3 +9 tickets

  • Inventory refresh spike
  • Stream-protocol parity
  • Prompt + context assembly
  • Message pipeline + compaction
  • Citation processing
  • Guardrails + model behaviour
  • Business skills as records
  • Cutover + rollout
  • Retire Python chat service

Plus re-scoped existing tickets: LEX-644 (Standalone tools ×16, + VFS-tool subsumption) and LEX-645 (Two-tier skills runtime).

M4 +7 tickets

  • Agent principal
  • Durable background runs
  • Event→run gate + bindings
  • Proposal entity
  • Review home v1
  • Egress rings + approval verbs
  • First trigger→agent flow

Later +2 tickets

  • defineAgent redesign refactor
  • Code execution sandbox

Sources: the three milestone requirement plans in platform-v3/docs/plans (2026-07-03-001/002/003); ticket descriptions to be minted from these on approval.