Work with intent. Work with intent.

What you get

Focused tools in the Lolaplex stack — shipped when ready, maintained for the long run.

• Issues

  Typed relations

  Link work with depends, refines, references, and evidences. Dependencies gate moves; traceability stays on the graph, not in comment threads.

• Views

  List, board, timeline

  Same issues, three lenses. Kanban for flow, list for density, timeline for baseline, forecast, and actual schedule layers on one bar.

• Identity

  Humans and agents

  Passkeys for people. DIDs, signed challenges, and bearer tokens for agents. One capability model — who may create, move, relate, and watch.

• Project

  Memory and lock

  Agent memory lives beside the board. Origins lock pins what ships. GitHub links are pointers, not a second source of truth.

How MORe fits

No launch theater. The board is a view over structured work — canonical specs and proofs live elsewhere.

1. 01

   One leading record

   Each issue answers one question at one level. Documents, boards, and exports are projections. When the record changes, every view follows — no parallel truths to reconcile later.

2. 02

   Trace the chain

   Need → requirement → solution → implementation → verification → acceptance. Use refines and references to walk the chain; evidences holds what proved it.

3. 03

   Schedule in layers

   Baseline, forecast, and actual on the timeline — three dates, one issue. Cut-over exports keep the kernel honest for offline validation.

4. 04

   Agents sign in

   Humans use passkeys. Agents resolve a DID, sign a challenge, or present a hashed bearer token. Same rails, same audit trail — automation is not a back door.