Pavilion · The engagement workspace

The workspace
an engagement deserves.

Pavilion gives each Vantalect engagement its own private workspace: the calendar, every recording and transcript, the documents your sponsor signs off, the discussion, the decisions, the action items, the measurement, and, at the close, an export that is yours.

Included with every Vantalect engagement. Not sold separately.

A glass-and-steel pavilion at blue hour on a still lake, one warm light glowing inside.

What the workspace holds

Everything the engagement produces.
Everything it needs from you.

One room per engagement, shared by Charles, your sponsor, and your engineers, with nothing scattered across inboxes and chat.

  • The calendar

    Every session from kickoff to the closing readout, with its attendees and its Zoom link, dated from the day access exists.

  • Recordings and transcripts

    Every session recorded with your permission, its transcript speaker-labeled and searchable, and a reviewed summary for the people who were not in the room.

  • Documents with sign-off

    The audit, the plan, the readouts, and the playbook, each an immutable version your sponsor comments on and accepts.

  • The discussion

    Threads anchored to the thing being discussed: a paragraph, a session, a decision, a task. Not a channel to scroll.

  • The decisions

    What was decided, the options considered, the reason, by whom, and when. Drafted from the transcript, published after review.

  • Action items and obligations

    Who owes what by when, on both sides, including the statement-of-work commitments week by week.

  • The measurement panel

    Wired to your Fulcrum installation: the baseline, the current factor, coverage, and the gate the second invoice depends on.

What the client sees

One record, in the order it happened.

Open a workspace and the engagement is laid out the way it ran: the weeks as a timeline, each session with its record, each document with its acceptance, and the handover archive at the end.

  1. 01

    The timeline

    Each week of the engagement is a stop on a timeline with its dates, next to what was left open, the latest session, and the deliverables checklist.

  2. 02

    The session record

    The agenda, a summary a consultant reviewed before publishing, the speaker-labeled transcript with a search box, and the decisions and tasks the session produced.

  3. 03

    Documents and acceptance

    Each document is an immutable version with a content hash. The sponsor accepts a version, and the acceptance records the statement, the version hash, and the time.

  4. 04

    The handover archive

    Every document, transcript, decision, task, and recording, with a manifest and hashes, generated at the close and on any day before it.

The same views fold into one column on a phone, so a sponsor can read the record the same way away from a desk.

See it in a sample engagement

Three engagements,
two fictional clients.

StrataForge Robotics and Seatlark, Inc. do not exist. We invented them so you could see a finished engagement, and each case study has a Pavilion section that describes the workspace for that engagement in words: the timeline, the sessions, the documents, and the acceptances. The product’s behavior is real; the client is not.

Want to see it live? Ask for a walkthrough when you book the call. A read-only demo workspace is planned once the interface is final.

How it works

From signature to handover.

  1. Step 1

    Set up in week one

    The workspace is created from the engagement’s template: the calendar, the deliverables checklist, the obligations, and the document slots appear, dated from the access date. Your sponsor and engineers are invited by email.

  2. Step 2

    Every session, kept

    Sessions are recorded on Zoom; the transcript, a reviewed summary, the decisions, and the action items appear on the session page within the hour.

  3. Step 3

    Documents, accepted

    The audit, the plan, the readouts, and the playbook are published as versions. Your sponsor comments on paragraphs and accepts the version; the checklist ticks itself.

  4. Step 4

    Exported, yours

    At the close, one archive of every document, transcript, decision, task, and recording, with a manifest and hashes. The workspace stays readable to you afterward.

Who does what

Seven roles, one room.

The sponsor and engineers see the published record. Nothing an agent drafts is visible to the client until a consultant has reviewed and published it.

RoleWhoCan
OwnerVantalectEverything: workspaces, templates, members, API keys, exports
ConsultantCharlesPublish documents, schedule sessions, attach recordings, record decisions, assign tasks, mark deliverables
SponsorThe client executive who signedAccept deliverables and readouts, see the measurement panel, comment, invite their own people
EngineerA client engineer on the named teamRead, comment, complete their tasks and obligations, open Fulcrum from the panel
ObserverAnyone else the sponsor invitesRead and comment
AgentA Claude Code session acting for CharlesPublish, attach, summarize, record, and read through the API and MCP, as its own identity in the audit log
GuestThe holder of a share linkRead one document or recording, with expiry, no account

Every surface, one service layer

The web app for people.
The API and MCP for the agents.

Charles’s agents publish summaries, documents, decisions, and tasks straight into the workspace, and each one signs the audit log as itself.

  • REST and SSE. Every resource under /api/v1/ with OpenAPI documentation, and a live event stream per workspace.
  • MCP server. More than 150 tools any MCP-capable agent can call: publish a document version, attach a recording, record a decision, create a task, snapshot the measurement, export the workspace.
  • Webhooks. Signed, retried, per workspace, for whatever your side wants to know the moment it happens.
  • Export. Every document as PubMark and PDF, every transcript, decision, and task as JSON, every recording, with a manifest and SHA-256 hashes.

The part most tools get backwards

Everything is left with you.

A consultant’s workspace usually vanishes with the consultant. Pavilion is built so the client keeps the room: the export, the read-only workspace, and the audit log of who saw what, when.

  • Your export, any time

    The sponsor can generate the full archive on any day, not only at the close.

  • Your data, your rules

    Nothing about your code leaves your repositories. The measurement panel copies figures, never records. Retention is yours to set; deletion is one request.

  • Your audit log

    Every view, download, publish, acceptance, and share-link use, with the person, agent, or service that did it.

Included with

Every Vantalect engagement.

Pavilion is not sold separately, so this page has no price. It comes with the work, and each engagement runs in its own workspace.

A glass-and-steel pavilion at blue hour on a still lake, one warm light glowing inside.

Client sign-in

How your people get in.

This site has no sign-in page. The sponsor and the named engineers are invited by email when the engagement starts and sign in from that invitation. If an invitation did not arrive, write to charles.sieg@vantalect.com.

Questions

What people ask first.

Can I buy Pavilion on its own?

No. Pavilion is included with every Vantalect engagement and is not sold separately, so there is no price and no sign-up.

Who can see what?

Seven roles decide: owner, consultant, sponsor, engineer, observer, agent, and guest. The sponsor and engineers see the published record. Nothing an agent drafts is visible to the client until a consultant has reviewed and published it.

Are my meetings recorded?

Sessions are recorded on Zoom with your permission, and the recording and transcript arrive in the workspace. A passage can be redacted from a transcript before it is published, and the redaction is logged.

What do I keep at the end?

One archive of every document and version, transcript, summary, decision, task, obligation, acceptance, and recording, plus the audit log, with a manifest whose hashes are re-verified from the archive itself. The workspace also stays readable to your people.

Is the sample engagement real?

No. StrataForge Robotics is a fictional company, and its two engagements are a demonstration. The behavior of the product is real; the client, its people, and its figures are not.

How do my people get in?

The sponsor and the named engineers are invited by email when the engagement starts and sign in from that invitation.

Zoom is a trademark of Zoom Video Communications, Inc. Claude Code is a trademark of Anthropic, PBC. Vantalect is not affiliated with or endorsed by either.

The next conversation

Let's define the result.

Pavilion comes with every engagement. Tell Charles which challenge is in front of you, and he will tell you which engagement fits and what it would measure.

Book a 15-minute call with Charles

Remote engagements nationwide.
Serving clients since 2020.