Portae · requirements · review · agent dispatch

Project work, structured for humans and agents.

Portae holds the work from first concept through requirements, reviews, backlog, agentic team management, implementation evidence, version control, defects, and messages. It is the shared operating surface for AI-era software delivery.

A product-style control plane with requirements lanes, Guide, agents, dispatch, and trace links

What is Portae?

Portae replaces disconnected requirements tools, chat threads, and agent handoffs with one continuous working surface. Documents become Decks; requirements, architecture records, test cases, backlog work, implementation evidence, defects, orders, and messages become Cards with stable IDs and typed links.

Start with a concept or source document and grow it into a structured specification Deck.
Carry User Requirements, System Requirements, Architecture, Test Cases, Backlog, Commits, and Defects together.
Review, annotate, comment, answer messages, and decide directly beside the work being discussed.
Let human colleagues and agentic teams operate the same living project surface.

Decks & Cards

Source specifications, user requirements, system requirements, architecture records, tests, defects, commits, orders, and messages all share one Card model with typed references.

Lane filtering

Click a Card and the lanes contract to its upstream and downstream neighbours: source spec, UR, SR, AR, TC, comments. The work map stays visible; the noise drops away.

Threaded review

Comments attach to Cards, carry discussion history, and preserve closure or postponement decisions next to the requirement or design point being reviewed.

Orders & Messages

ORD and MSG Cards carry work to named agents and route messages between humans and AI systems so dispatch remains visible inside the normal traceability surface.

Agent-operable

Agents create Decks, split documents, add requirements, export Decks, and answer review work through the same DB-backed surface as the human UI, with no privileged side channel.

Guide chat

The violet Guide button opens a conversational dispatch surface. Today it helps with the GUI; next it can analyze software, handle Portae work, and carry context toward the Meaning Graphs UML interface.

One surface for people and agents.

Human operators work through the browser surface: reading, editing, reviewing, annotating, and deciding beside the project material. Agents work through the same database-backed model: the same Cards, links, comments, and status transitions. Decisions made through one surface are immediately visible through the other.

A human can provide a file and have an agent create a specification Deck from it. From there, agents can pick up the detailed User Requirements, System Requirements, Architecture, Test Cases, Backlog, Implementation and Commits, and Defects. The handoff stays structured, inspectable, and ready for another human or agent to continue.

Rich context menus to add Cards, add Decks, annotate requirements, comment on decisions, and answer messages.
Comments can come from humans or agents, with answers, discussion, and decisions preserved beside the Card.
Multiple agents can work together on the same project surface without losing ownership or evidence.

Portae requirements board with SPEC, UR, SR, and AR lanes — Requirements, system requirements, architecture records, and traceability visible in one board.

Dispatch is first-class project data.

Orders flow from decision to assignee, through execution, readiness, and validation. Messages flow peer-to-peer, then remain attached to the work they concern. ORD and MSG Cards sit inside the same Decks as requirements, architecture, tests, commits, and defects.

All-in-one flowfrom concept to commits

Traceable workCards, links, comments

Agent-readyAPI + dispatch records

Portae dispatch and mailbox view with agents and messages — Dispatch, mailbox, officers, Guide, and messages live beside the work they coordinate.

The board-shaped view of the same truth.

Portae is the perspective where project truth becomes something a human can work with directly. Requirements, architecture decisions, tests, defects, dispatch messages, implementation evidence, and review comments are not scattered across separate tools. They become typed Cards with stable identity, links, status, and history.

That shape matters because AI-era work moves quickly. A requirement can produce architecture, an architecture decision can open assignments, a defect can require a test, and an agent response can become evidence. Portae keeps those movements inspectable instead of letting them dissolve into tickets, chat fragments, and private memory.

Portae is not just requirements management. It is the board view of the model: what the work is, who is touching it, and why the next step is justified.

This is also why Portae and Meaning Graphs belong together. Portae can hold the requirement, decision, assignment, and review context; Meaning Graphs can show how the code and UML evidence support that context. They are two perspectives over one Library, not two competing systems.