The Brief

Every word heard. Every decision kept.

The Brief is the process side of Nexora. It reads your discovery workshops, extracts requirements cited to the second, finds the contradictions between rooms, takes each one to the person who owns the answer, and assembles the signed blueprint that everything downstream is derived from.

The Brief: the program's front page, leading with the one ruling that matters today
The Brief, live. The first ruling of the day, with the words behind it and the timestamp.81 rulings waiting · 4,209 requirements captured · 72 fit themes mapped

From a room full of people to a record you can sign.

  1. Listen

    Recordings and documents in, from your own Drive. Originals never leave it.

  2. Extract

    Atomic requirements, each cited to the second. Uncited is invalid.

  3. Contradict

    Disagreements found across sessions, both positions quoted to the second.

  4. Rule

    A named expert decides. The ruling binds, and records what it rejected.

  5. Sign

    A blueprint assembled from rulings. Immutable once signed.

  6. Derive

    Specs, tests, change impact, training and BPMN, all from the signed design.

One page each morning: what needs you.

The program's front page leads with the one decision that matters today, quotes the words behind it with the timestamp, and says how many artifacts wait on it.

The Situation

Rulings waiting, deliverables ready, AI spend against value delivered.

The Queue

Ranked by what each ruling unblocks, not by when it arrived.

What Moved

Every entry carries its receipt.

The Manifest

Every deliverable SAP Activate expects — 80 across six phases — and where each one stands.

The Brief on the demo record: a revenue-recognition ruling holding twelve artifacts
Aiden

The one who read everything, and remembers who said it.

Aiden is Nexora's reader. Ask it anything about the program — what is waiting on you, where a decision came from, what breaks if you re-rule C-05, what the legacy system actually does today — and it answers from the record, with the ruling, the session and the second attached.

Reads, never writes

Aiden cannot add a fact, correct a ruling or infer a decision. The record changes only through the four human gates.

Every answer cites

Decision, session and evidence chips under every claim. Open the citation before you act on an answer.

Two scopes

Record answers from confirmed memory. As-Is answers only from what Forge read out of the running system — what exists today, nothing to-be.

Cost in the open

Requests and spend are metered per day and shown to the person asking.

A
Aiden
Reads the record · never writes
RecordAs-Is
Why did we defer service credits?
• Walking the decision graph

Service credits were deferred to the parent landscape. The process owner ruled it in session 3 and recorded the two options rejected: building them locally, or dropping them.

Twelve artifacts rest on that ruling — the revenue-recognition design, two test families and the finance change-impact notes. None is on superseded ground.

DC-04S-03 · 15:47EV-212BP-2.4
Ask the record…
AI-generated. Verify figures before acting.1 / 200 today · $0.013
The Desk: produce, prove and remember commissions, each naming its reviewer and approver

The Desk. Everything you can ask for.

Every line is something you commission. Each has a reviewer, and each ends with a person.

Produce

Ingest a session · Extract requirements · Find contradictions · Map fit · Assemble the blueprint

Prove

Draft the test plan · Draft scenarios and cases · Evaluate results · Draft the change plan · Build a ruling pack

Remember

Ask the record · Trace a change · Document the process · Draw it in BPMN 2.0 · Export the memory as JSONL

The Brief hands Forge its specifications, and Manage its gates.

A signed section becomes the specification Forge builds from, with acceptance criteria cited back to the room. An open critical conflict is what keeps a Manage gate shut. Same record, three faces.