The outcome you are walking toward
A diligence briefing you can give without collapsing Scaffold into "another job-site app." You leave able to name what Scaffold owns as the build vertical orchestrator, how it sits on Business OS, which public docks carry the substrate hops, and what remains designed-for / staged — without inventing schedule variance, safety rates, or shipped coverage you have not seen.
Scaffold is an orchestration, not a point tool
Scaffold is the adaptive field OS for construction networks. The public silo is MCV.BUILD — Scaffold. Category-level posture only: project tools capture tasks and photos; Scaffold is designed to turn every job site into a fully instrumented field organism for progress, safety, crew coordination, equipment utilization, and method improvement — even in harsh, changing, low-connectivity environments. The job site is temporary; the organism is designed for rapid deploy, teardown, and redeploy across a portfolio of projects.
MCV.BUILD is in staged rollout. The field OS, agent team, and hardware kits described publicly are designed capability, being deployed progressively with early partners — not a generally shipped product. Prefer "designed to" over present-tense availability claims.
If a briefing treats Scaffold as a standalone field app beside Business OS, ask how a critical safety or progress loop crosses sensing, interconnect, events, judgment, action, and forging without a second integration project per hop. The signal-order walkthrough is Walk the six-system substrate chain.
What Scaffold specializes (honest domains)
Public depth on the build silo organizes around operating domains — diligence vocabulary, not a weighted scorecard:
- Field progress versus plan — structured observations, photos, and progress entries as one field record that back-office systems read once. The discipline is build field record discipline.
- Safety observations — PPE, fall risk, unsafe conditions, and near-miss capture designed to stay live offline; safety loops are sacred.
- Crew coordination — presence, check-in, certification and fatigue signals that feed task rebalance without inventing headcount theater.
- Equipment utilization — machine and asset presence as first-class signals on the Mesh fabric.
- Method improvement — outcomes that turn site experience into better playbooks under governance, not a next-week slide.
Named-vendor battle cards stay internal. Public differentiation stays category-level.
Scaffold Field — primary agent on the ground
Scaffold Field is the named primary agent of the build vertical. Mandate: field progress versus plan, safety observations, crew coordination, equipment utilization, and method improvement on live sites. Style: direct, rugged, optimized for clarity in noisy, fast-moving environments. Signature focus: what is actually happening on the ground right now, and is it safe.
It is designed to live inside site loops (PPE breach, near-miss, progress capture, utilization variance) alongside supervisors — not as a next-day dashboard the office opens after the shift. Shared teammates (Sentinel, Atlas, Nexus, ForgeMaster) enrich context; Scaffold Field owns the build-lane mandate.
Authority still sits on the shared floor: irreversible classes stay gated; brand scope fails closed; reconstructability lives in the audit trail. Counsel walks that story through Verify what an agent is allowed to do and governed agent boundaries.
Substrate docks Scaffold depends on
Scaffold is a specialized orchestration on the MCV substrate. Public docks you can open in a briefing:
- Mesh — rugged devices, wearables, and site assets as a living interconnect fabric. Interconnect fabric is not data fabric.
- Synapse — real-time safety and progress loops between field nodes.
- Forge — outcomes that turn site experience into better methods and skills under governance.
- Pulse / Cortex / Aria complete the chain narratively; product docks for Mesh, Synapse, and Forge are the ones to name aloud first.
Composition of kits, agents, verticals, and Franchise OS is Name what the organism is made of.
Hardware and offline — strictest field contract
The physical posture for one Scaffold job site is Spec the hardware for a Scaffold job site: rugged edge, industrial networking, high-endurance power, wearables and presence, harsh-environment vision and sensors — all reference configurations finalized per site survey. Scaffold carries the strictest offline contract of any vertical: access and presence recording, critical safety alerting, local progress and observation capture, and equipment utilization logging are designed to continue offline; safety observations store-and-forward with integrity; silent loss of safety or presence records is forbidden. The careful public contract is Read the offline contract your locations run on.
How to use this leaf in a briefing
- Open the silo first: MCV.BUILD — Scaffold.
- Name Scaffold as vertical orchestrator on Business OS, not as a project-management replacement alone.
- Hedge availability explicitly: staged rollout, designed capability — not generally shipped.
- Walk Mesh → Synapse → Forge docks before any "AI job site" demo.
- Push autonomy claims back to gates and evidence — never to a slide metric or invented job KPI.
- Separate location runtime from network learning (Business OS vs Franchise OS).
- Pair with the property sibling when the portfolio spans assets: Brief Domain without mistaking it for a PMS stack.
Non-goals for this leaf
- No schedule-variance percentages, safety-rate claims, uptime guarantees, or invented customer logos.
- No fake job metrics, headcount theater, or certification badge theater.
- No named-vendor battle cards.
- No present-tense claim that every Scaffold kit path or vision zone ships at equal maturity on day one.
When Scaffold is clear, continue composition via organism composition and counsel review via diligence resources.