ARCLAVE
The Chief Architect’s Guide

Welcome to Arclave.

You run the meeting. You weigh the options. You make the call. Arclave walks beside you and makes every step of that decision provable — before, during, and long after the room empties.

⏱ About thirty minutes from sign-in to your first Sealed decision

A note on this guide: it describes the complete Arclave v1 experience, end to end. A few screens are design previews of features now in engineering, and two product choices — the meeting consent posture and the first two freeze adapters — remain open on the roadmap. The validation instrument is settled: the six-gate Well-Made Decision Test.

Before you begin

Arclave in six ideas.

Everything else in this guide is these six ideas wearing different screens.

01

Assurance, not authority.

Arclave never makes the decision. It makes sure the decision is worth making — complete, challenged, evidenced, and on the record. The call stays yours. Permanently.

02

The Case File.

Every decision lives in one place: the problem, the options, the evidence, the people, the dissent. Not scattered across nine tabs and three inboxes.

03

The Digital Twin.

A living model of your enterprise with a long memory and a fast imagination. It recalls every precedent you ever Sealed and plays out tomorrow before you commit to it.

04

The Well-Made Decision Test.

Six gates every decision must clear: Complete, Consistent, Conformant, Evidenced, Recorded, Accountable. Clear all six and the decision earns its Seal.

05

The Seal.

A tamper-evident stamp of assurance. Once Sealed, a record never changes — and anyone, including a regulator, can verify it to the byte.

06

A layer, not a replacement.

Arclave sits over Teams, Outlook, SharePoint, Jira, and SAP LeanIX. Your tools keep their jobs. Arclave masters exactly one thing: the ratified decision.

Day one · about 15 minutes

Set up once. Decide forever.

Four steps, one cup of coffee. You sign in with the Microsoft account you already own, connect the tools you already use, and seat the people already on your board.

1

Sign in with Microsoft.

Go to app.arclave.com and choose Continue with Microsoft. Your work account is your Arclave account — no new password to invent, no new password to forget.

1
app.arclave.com
Welcome to Arclave
The Decision System of Record
Continue with Microsoft
Single sign-on via Microsoft Entra ID
1Click Continue with Microsoft. Approve the sign-in prompt from your organization. That’s the whole step.
2

Connect Outlook, Teams, and SharePoint.

Open Settings → Connections. Each tile explains exactly what the connection is for — nothing connects without your click, and each one works alone.

1 2
app.arclave.com/settings/connections
Connections
Arclave is a layer over your tools. Connect the ones your board already uses.
Ou
Microsoft Outlook
Announce Sealed decisions to your mailing lists — sent from your own address
Connect
Tm
Microsoft Teams
Meeting Presence in your Architecture Review Board calls, plus decision cards in channels
Connect
Sp
SharePoint
Evidence stays in SharePoint — Arclave links to it and fingerprints it, never copies it
Connect
Lx
SAP LeanIX
Decisions cite your portfolio facts; Sealed decisions project back as decision cards
Connected ✓
1Click Connect on Outlook and Teams. A standard Microsoft consent screen opens; approve it once.
2Connect SharePoint so evidence can be linked by reference. Already-connected tools show a green check.
Tip

Evidence never moves. Arclave links to the document where it lives and stores its fingerprint — a cryptographic hash — so the record can later prove the file never changed. Your files stay exactly where your security team likes them.

3

Seat your board.

Open People and give each person a role. Three roles cover an Architecture Review Board (ARB): the Decider ratifies, Reviewers challenge and annotate, Viewers read. One rule above all: every decision names exactly one accountable decider. Today, that’s you.

1
app.arclave.com/people
People & roles
Roles decide who may write, challenge, and ratify. Every action lands on the audit chain.
You
You — Chief Architect
Chairs the board · ratifies decisions
Decider
PN
Priya N.
Security architecture
Reviewer
MT
Marcus T.
Platform engineering
Reviewer
EV
Elena V.
Risk & compliance
Reviewer
+
Invite more
Auditors and executives usually join as Viewers
Invite
1Confirm your own Decider chip. Reviewers and Viewers accept an email invitation — that’s all they need to do. (In this release the invitation is a shared front-door link: your colleague signs in with Microsoft, appears under “Awaiting admission,” and you admit them with one audited click. Email invitations arrive with the Outlook connection.)
4

Bring your history in. Optional · recommended

Point the importer at the SharePoint library or Confluence space where your old decision records sleep. Arclave brings them in as-found — verbatim, with source, author, date, and fingerprint — and marks them Registered, never Sealed. History is preserved, never retouched.

1
app.arclave.com/import
Import complete
SharePoint · “ARB Minutes 2019–2026” · finished 4 minutes ago
128
records imported
128
marked Registered (as-found)
0
Sealed retroactively — by design
!
Your Gap Report is ready.
62% of your historical decisions name no second option considered · 41% link no evidence · 17% name no decider.
Open the Gap Report
1Open the Gap Report. It reads uncomfortably at first — and it’s the most honest baseline your governance ever received.
Why nothing old gets a Seal

The Seal means one thing: this decision passed the gates. Stamping it on history that never took the test would debase it on day one. Old records stay Registered with full provenance; any of them can graduate to Assured later by actually passing the gates — with the graduation on the audit chain. And the gaps the report finds belong to the tooling era, never to the people. Your corpus did well to survive at all.

The day before · about 10 minutes

Frame it before you fight about it.

An assured decision starts before anyone joins the call. Ten minutes of framing saves an hour of circling — and the twin does its homework overnight.

1

Open a Case File.

From the Console, click New decision. Name what you’re deciding, why now, who sponsors it, and what kind of decision it is. That’s the whole form.

1
app.arclave.com/decisions/new
New decision
A Case File opens as a draft. Nothing is Sealed until the gates pass and you say so.
Retire the legacy message bus
Vendor support ends Q2 2027; capacity trending toward its ceiling
Marcus T. — Platform
Architecture · platform lifecycle
Create Case File
1Click Create Case File. The case opens with an assembly checklist — the next step fills it.
2

Assemble the case.

The checklist asks for the ingredients of a real decision: at least two options, evidence linked from where it lives, impacts, and the people affected. One option is a conclusion, not a decision — Arclave holds the line on two.

app.arclave.com/decisions/draft-208
Retire the legacy message bus
Case assembly · draft
Options — 2 of 2 minimum
A: Migrate to the event platform now · B: Extend bus support 12 months, migrate later
Evidence — 5 linked
Capacity study, vendor end-of-life notice, cost model, dependency map, migration plan — linked from SharePoint, fingerprinted
Impacts — 3 named
Order processing, partner integrations, the data streaming team
Stakeholders — 1 missing
Security architecture reviewer not yet attached
Add
3

Read the twin’s pre-read.

Overnight, the Digital Twin does what a great chief of staff would: it searches every decision your enterprise ever Sealed, plays your options forward, and lists what the case still lacks. You walk into the room already knowing what’s missing.

app.arclave.com/decisions/draft-208/preread
Pre-read · Thursday’s board
Generated by the Digital Twin · 6:00 AM
Institutional memory

Related precedent: DR-2026-014 — Integration Platform Consolidation, Sealed 12 Mar 2026. Option B extends a platform that decision marked for exit. The delta is attached.

Simulation

Under Option B, the twin projects the bus crosses its safe-capacity ceiling in Q3 2027 — one quarter before the deferred migration completes. Confidence: moderate; the projection and its inputs are attached.

Completeness

Two items still open before the gates can pass: no rollback plan on the record · security impact unassessed.

4

Invite Arclave to the meeting.

On the Case File, switch on Meeting Presence and pick Thursday’s board call. Arclave joins your Teams meeting the way any attendee would — visibly, with everyone’s consent, and with nothing kept it doesn’t need.

1
app.arclave.com/decisions/draft-208
Meeting Presence
Live assurance during the meeting where this decision is made
Tm
Architecture Review Board — weekly
Thursday, 9 July 2026 · 10:00–11:00 · Microsoft Teams
Presence on ✓
Transcript-less mode
Everyone sees a banner and consents on entry. Arclave listens for the decision, keeps the structured record — and keeps no recording and no transcript.
1Toggle Presence on for the meeting where the call will be made. Attendees consent on entry; the banner stays visible throughout.
Thursday, 10:00 AM · live

Run the room. Arclave watches your blind side.

You facilitate exactly as you always do. Arclave sits in the side panel and speaks only when assurance requires it — in four kinds of sentences, and only those four.

The four sentences Arclave speaks

Completeness

“What’s still missing.”

“No rollback plan is on the record yet.” The case’s open items, stated plainly, so the room can close them while it’s still cheap.

Memory

“What you already decided.”

“This conflicts with DR-2026-014, Sealed in March — here’s the delta.” The enterprise’s own precedent, recalled at the exact moment it matters.

Simulation

“What tomorrow looks like.”

“Under Option B, the twin projects a capacity breach in Q3 2027.” Each option played forward against the model of your estate, error bars included.

Rules

“What your governance forbids.”

“Option B keeps an end-of-life platform in production past policy EOL-001.” Your own rules, applied as code — before the decision, not in the post-mortem.

Why Arclave never says “choose Option A”

We tested the tempting promise — formally, in pre-registered, openly published research. A board of artificial experts did not out-decide its own best single member, and it was never staged against your human experts at all. So Arclave routes all of its intelligence into checking rather than choosing: it recommends what to fix, never what to pick. The judgment stays where it belongs — with you and your board.

1

Watch the panel as the discussion moves.

Arclave recognizes when a decision is forming and raises interventions in the side panel — quietly, to the room, with receipts attached. Nothing interrupts the speaker; everything lands on the record.

1 2 3
Microsoft Teams — Architecture Review Board · weekly
YouYou — chairing
PNPriya N.
MTMarcus T.
EVElena V.
Arclave · assurance panel
Memory

Option B conflicts with DR-2026-014, Sealed 12 Mar 2026. View the delta →

Simulation

Option B: safe-capacity ceiling crossed Q3 2027, before migration completes.

Completeness

Still open: rollback plan · security impact.

1Read interventions as they arrive. Each one cites its source — a precedent, a projection, a rule, or the case itself.
2Click any card for the receipts — the Sealed precedent, the projection’s inputs, the exact policy line.
3Click “What’s missing?” whenever you want the full picture. That’s the next step.
2

Ask the question that changes the meeting: “What are we missing?”

Say it out loud or click it. Arclave answers with the gate preview — the six gates of the Well-Made Decision Test, each one green or amber, with the exact items still open. Assign each open item an owner in the room, and watch the gates close in real time.

1 2
Arclave panel — gate preview
Before this becomes a decision
The Well-Made Decision Test · live preview · 10:37 AM
Complete
Two options weighed · impacts named
!
Complete — 1 item open
No rollback plan on the record
Assign: Marcus T.
!
Evidenced — 1 item open
Security impact memo not yet linked
Assign: Priya N.
Consistent
DR-2026-014 conflict surfaced — resolve or waive on the record before ratifying
Conformant
Policy EOL-001 satisfied by Option A · violated by Option B (flagged)
Recorded · Accountable
Capture is live · decider named: you
1Assign each open item to a person in the room. “Marcus owns the rollback plan” takes four seconds now and saves a follow-up meeting later.
2Watch the gate flip green the moment the item lands on the record.
3

Play tomorrow before you commit to it.

Click Run what-if and the Digital Twin plays each option forward against the living model of your estate — capacity, cost, timeline, dependencies. Projections come with stated confidence and every input on display. The twin shows its work; the room draws its conclusions.

Arclave panel — what-if simulation
What-if · both options, played forward
Digital Twin projection · confidence: moderate · inputs attached
Option A — migrate now projects clean
Bus load through Q2 2027
Migration complete
Wave 1 lands Q4 2026 · capacity steady · consistent with DR-2026-014
Option B — extend 12 months breach projected
Bus load through Q3 2027
Migration complete
Ceiling crossed Q3 2027, one quarter before cutover · policy EOL-001 flag
4

Call it. That part is all you.

When the room is ready, open the Decide sheet. Pick the verdict, attach the conditions the discussion produced, and record the dissent — in full. Dissent is a first-class citizen of a well-made decision; your successor will thank you for it.

1
Arclave — Decide · Retire the legacy message bus
Your verdict
Ratified by the accountable decider — you. Arclave records; it never votes.
Approve with conditions — Option A
Selected
Approve
Reject
Defer — name what unblocks it
1. Rollback plan filed before migration wave 1 — owner: Marcus T.
2. Security impact assessment linked within 30 days — owner: Priya N.
Elena V. prefers Option B: the migration team is stretched; twelve months of headroom lowers delivery risk. Recorded in full.
Record verdict
1Click Record verdict. The meeting can end; the record is already writing itself.
After adjournment · about 5 minutes

Seal it. Around here, that’s a verb.

You adjourn. The record is already written. Read it once, run the test, hand the future its baton — and press Seal.

1

Review the draft record.

At adjournment the Case File assembles itself into a draft Assurance Record: who attended, which options were weighed, every intervention raised and how the room answered it, the evidence links, your verdict, the conditions, the dissent. Read it once. Fix anything the room said differently.

2

Run the Well-Made Decision Test.

Six gates, scored like a chain — the weakest link is the score. When a gate fails, Arclave names the exact sentence to fix. No mysteries, no vibes.

1
app.arclave.com/decisions/draft-208/test
The Well-Made Decision Test
Retire the legacy message bus · all six gates must pass
Complete
Two real options weighed · impacts named · rollback plan filed at 11:52 AM
Consistent
DR-2026-014 conflict resolved on the record: Option A aligns with the consolidation path
Conformant
Policy EOL-001 satisfied · no rule violations under Option A
Evidenced
6 documents linked by reference and fingerprinted, security memo included
Recorded
Verdict, two conditions, one dissent, full rationale — all on the record
Accountable
One named decider: you · ratified 9 July 2026, 11:47 AM
6 of 6 gates passThis decision is eligible for the Seal.
1Six green gates unlock the Seal. An amber gate shows you the one sentence standing between you and it.
3

Hand the future its baton.

A Sealed decision isn’t a finish line — it’s a handoff. Three fields ride inside the Seal: the open conditions, the outcome you expect, and the date you’ll check. Six months from now, nobody will wonder what this decision promised.

app.arclave.com/decisions/draft-208/baton
The baton
What this decision hands to the future — carried inside the Seal
Rollback plan before wave 1 · security assessment within 30 days
Migration wave 1 complete by Q4 2026 with zero critical incidents
15 January 2027
4

Press Seal.

Arclave stamps the record with a cryptographic fingerprint, files it on the tamper-evident chain, and mints its Decision Record number. From this second the record never changes — corrections append beside it, never over it — and mastery of the decision transfers to Arclave. Wherever your meeting notes live, they now point here.

1
app.arclave.com/decisions/DR-2026-041
DR-2026-041 · Sealed
Retire the legacy message bus · Approved with conditions · 9 July 2026
SHA-256 · a4d3e8fb 9c02 71e6 44b8 0d5f 27a1 c39e 88f4…
1This is the moment the wordmark turns into a verb. “Is it arclaved yet?” — expect to hear it within the week. You archive a document. You arclave a decision.
What the Seal actually promises

Three things, no more and no less: this record passed all six gates; a named human ratified it; and from the moment of Sealing, any change to a single byte becomes detectable by anyone who checks. The Seal never claims the decision is right — it proves the decision was well made. Time gets to judge the rest, and the Outcome Ledger gives time its ledger line.

Two minutes later

Tell everyone. Once. On the record.

A decision nobody hears about is a decision that gets re-litigated in six months. From the Sealed record, Arclave drafts the announcement, you approve it, and it goes out through your own Outlook and Teams — then logs exactly who was told, and when.

1

Open Announce on the Sealed record.

Pick the audience: your Outlook mailing list, your Teams channel, or both. Arclave writes the draft from the record itself — the verdict, the why, the conditions. No spin is available to it; it can only say what the record says.

1 2 3
app.arclave.com/decisions/DR-2026-041/announce
Announce DR-2026-041
Drafted from the Sealed record · sent through your connected accounts
Ou
Email · Outlook
To: ARB-Decisions (distribution list, 214 members)
On ✓
Tm
Teams · post a decision card
Channel: Architecture Review Board
On ✓
PREVIEW · EMAIL
Decision Sealed: DR-2026-041 — Retire the legacy message bus
Verdict: Approved with conditions — migrate to the event platform; the bus retires by Q2 2027.
Why: Vendor support ends Q2 2027; the twin projects a capacity breach under any deferral; the move aligns with DR-2026-014.
Conditions: rollback plan before wave 1 (Marcus T.) · security assessment within 30 days (Priya N.).
Review by: 15 January 2027 · Dissent recorded and preserved.
View the full record
1Choose the mailing list. Arclave reads your Outlook distribution lists; pick the one your organization already watches.
2Toggle the Teams card on. The channel gets a compact decision card with the same canonical link.
3Click Approve & send. Arclave sends the email from your address, posts the card, and completes the task — then writes both acts onto the record’s audit chain: who was told, when, through what.
Tip

The announcement links to the record; it never attaches it. One canonical copy exists, forever, at one address. Forwarded email rots — the link stays true.

The weeks after · mostly automatic

The decision keeps working after you stop.

Most tools forget a decision the moment it’s made. Arclave is just getting started: conditions get tracked, the review date arrives on schedule, and the outcome gets written down next to the promise.

1

Watch the conditions discharge.

“Approved with conditions” where nobody checks the conditions is theater. Each open condition sits on your Console until it’s discharged with evidence — and the discharge itself lands on the audit chain.

app.arclave.com/decisions/DR-2026-041
Conditions · DR-2026-041
2 attached at the Seal · 1 discharged · 1 open
Rollback plan before wave 1
Discharged 16 July 2026 · plan linked and fingerprinted · owner: Marcus T.
!
Security assessment within 30 days
Open · due 8 August 2026 · owner: Priya N.
12 days left
2

The review date arrives. Answer four questions.

On 15 January, Arclave taps you on the shoulder: the baton said to check. The After-Action Review asks exactly four questions — what did we expect, what actually happened, why the difference, and what changes next.

app.arclave.com/outcomes
Review due today · DR-2026-041
After-Action Review · the outcome writes beside the decision, never over it
Wave 1 complete by Q4 2026, zero critical incidents
Wave 1 completed 11 Dec 2026 · one minor incident, resolved in 4 hours
Partner integration cutover ran two weeks long; the rollback plan was never needed
Add partner-cutover lead time to the migration playbook; carry into wave 2 planning
File the outcome
Outcomes calibrate. They never re-grade.

The Sealed record stays exactly as the room made it — that’s the whole point of a Seal. The outcome writes beside it on its own ledger, so your enterprise learns whether its decisions keep their promises without ever rewriting history. Two ledgers: what you decided, and what happened. Auditors dream about this.

3

Close the loop with the Three R’s.

Every reviewed decision earns one of three fates: Reaffirm it as-is, Revise it with a new decision that cites this one, or Retire it with honors. No zombie decisions haunting the estate, no “wait, is that still policy?”

4

Then watch the interest compound.

Six months from now, in a different meeting, someone proposes rebuilding on the old bus. The twin clears its throat: “DR-2026-041, Sealed in July, decided otherwise — here’s why, and here’s how it turned out.” One sentence, and a settled argument stays settled. That’s institutional memory earning interest. That’s the point of all of it.

Keep this page

The whole system on one screen.

The six gates — the Well-Made Decision Test

  1. Complete — at least two real options, impacts named, nothing material missing.
  2. Consistent — squares with your Sealed precedent, or the conflict is resolved on the record.
  3. Conformant — passes your own rules and policies, applied as code.
  4. Evidenced — every load-bearing claim links to a fingerprinted source.
  5. Recorded — verdict, conditions, dissent, and rationale, all on the record.
  6. Accountable — one named human decider ratified it.

Scored like a chain: the weakest gate is the score.

The four sentences Arclave speaks

  1. Completeness — “Here’s what the case still lacks.”
  2. Memory — “Here’s what you already decided, and the delta.”
  3. Simulation — “Here’s what tomorrow looks like under each option.”
  4. Rules — “Here’s what your own governance forbids.”

Never a fifth sentence. Never “choose B.” It recommends what to fix, never what to pick.

Five things Arclave never does

  1. Never votes, never decides. The verdict belongs to a named human. Always.
  2. Never Seals what never passed the gates. Imported history stays Registered, as-found.
  3. Never edits a Sealed record. Corrections and outcomes append beside it.
  4. Never moves your files. Evidence stays home — linked by reference, fingerprinted.
  5. Never holds your record hostage. Leave any time with a complete, verifiable export.

Words to know

Case File — one decision’s single home DR — Decision Record, the minted number The Seal — tamper-evident stamp of assurance Registered vs Assured — as-found history vs gate-passed decisions The baton — conditions + expected outcome + review date, inside the Seal Digital Twin — precedent memory + what-if simulation Meeting Presence — Arclave in the room, with consent Gap Report — what your historical corpus never wrote down Outcome Ledger — what happened, beside what was decided arclave — (v.) to lock a decision so it holds; to make it provable