The sample engagement

Two engagements for one fictional client.

StrataForge Robotics does not exist. We invented it so you can see a finished engagement in Pavilion: a six-week security Hardening and a six-week cost Optimization, each with its sessions, summaries, documents, decisions, and acceptances in place.

A demonstration with invented people, accounts, and figures. The product's behavior is real; the client is not. This page describes the record in words.

A robotics warehouse at blue hour: rows of low autonomous robots parked at charging docks along a long aisle, one amber lamp glowing.

The client home

Two engagements, two private workspaces.

A client sees where each engagement stands from one page, and opens each record separately. Both of StrataForge's engagements are concluded, and each ended at its closing gate.

  • AWS Security, Compliance & Governance Audit

    The six-week security Hardening, July 13 to August 21, 2026. The client home reads: closing gate passed on 08/21/2026, second invoice issued.

    See it in a sample engagement

The timeline

Six weeks, one stop each.

The cost Optimization as its workspace lays it out, from the kickoff on August 24 to the handover on October 2, 2026. The security Hardening runs the same shape from July 13 to August 21.

  1. Week 1 · Aug 24–28Baseline and inventory
  2. Week 2 · Aug 31–Sep 4Find and rank
  3. Week 3 · Sep 7–11Quick wins
  4. Week 4 · Sep 14–18Rightsizing and commitments
  5. Week 5 · Sep 21–25Architecture and guardrails
  6. Week 6 · Sep 28–Oct 2Measure and hand over

What the client sees

A record you can read in order.

These are the four places a StrataForge reader goes, described as the sample has them.

  1. 01The client home

    Two engagements, side by side. One card for each, with its dates, its state, its outcome at the closing gate, a link to the record, and a link to the handover archive.

  2. 02The overview

    Where it stands. The timeline above, then what was left open at the close, the latest session with its published summary, the deliverables checklist, and the documents published most recently, each marked accepted.

  3. 03A session

    The kickoff, with its record. The agenda, a summary a consultant reviewed before it was published, the speaker-labeled transcript with a search box, and the decisions and tasks the meeting produced. In the sample the recording is withheld and the page says so, so the transcript stands alone.

  4. 04A document

    Version 1 of the week 1 spend baseline, as published. Its contents list, a PDF and the source, the version's SHA-256, and the sponsor's acceptance recorded against that version, with a place for comments on any paragraph.

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

What is real

The client is invented.
The behavior is not.

Demo mode. Every record here belongs to StrataForge Robotics, a fictional company. Editing is disabled. This is the notice the app shows on every screen of the sample.

Invented

  • The company, its people, its accounts, and every figure in them.
  • The email addresses, which are on a domain that cannot receive mail.
  • The transcripts, written for the sample.

The product, as it runs

  • Summaries went through the review gate before they were published.
  • Each deliverable carries its document as evidence, and each acceptance names the version it covers.
  • The record exports as one archive with a manifest and hashes.

Want to see it live? Ask for a walkthrough at info@vantalect.com.

Included with every engagement

Built for one occasion.
Handed over when it ends.

Every Vantalect engagement runs in a Pavilion workspace, set up in week one and exported to you in full at the close. It is not sold separately.

See the engagements

Remote engagements nationwide.
Pavilion, a Vantalect app.