vcubed

Applications · Section 09 · Applications 01–06

Business documents

Proposals, statements of work, technical requirements, reports and executive summaries.

Proposal

Apply the system by role. A workstream family is useful only when it helps the reader navigate this artifact.

Core

Sapphire cover and navigation anchor

Workstream

One family may lead a focused proposal; a multi-workstream proposal uses each family in its own section

Status

Risks, milestones, decisions and delivery health only

Statement of work

Apply the system by role. A workstream family is useful only when it helps the reader navigate this artifact.

Core

Parchment and Nocturne, restrained

Workstream

Optional and subtle; commercial and contractual pages stay core-neutral

Status

Only where a genuine state is communicated

Technical requirements

Apply the system by role. A workstream family is useful only when it helps the reader navigate this artifact.

Core

Core neutral reading environment

Workstream

Local, for system layers, requirement families or architecture regions

Status

Validation, readiness, acceptance and risk

Reports and summaries

Begin with a core-neutral reading environment. Use workstream colour to signpost substantive sections and status colour only when reporting current state.

  1. 01Lead with the decision, outcome or required action.
  2. 02Keep contractual, commercial and approval pages core-neutral.
  3. 03Make evidence and caveats easy to find.

Business-document examples

The examples below show the rules applied to a cover, a contractual schedule and a technical requirements page.

vcubed contextual Sapphire lockupProposal · illustrative

Claims triage, from prototype to production

Prepared for a national insurer · RFP 2026-118

Proposal cover. Sapphire anchors the document; three workstream families identify the sequences inside.

Statement of workSchedule 2 · 4 of 11

Deliverables and acceptance

Retrieval service, stagingWk 6
Production-readiness reviewWk 9
Runbook and support handoverWk 12

SOW schedule. Core-neutral because the page is contractual and carries no state.

Technical requirements§4.2

Non-functional requirements

NFR-01 · MODEL
p95 under 250 ms✓ Verified
NFR-02 · DATA
Residency held in-region✓ Verified
NFR-03 · ADOPT
Fallback path usable▲ In test

Requirements page. Family prefix and status label keep colour from carrying meaning alone.

Production standard

The implementation profile defines the minimum structure required before a business document is ready to distribute.

01

Proposal

Core cover, decision-led executive summary, labelled workstream dividers, explicit assumptions and evidence adjacent to claims.

02

Statement of work

Core-neutral contractual pages, numbered deliverables, acceptance criteria, dates, owners and change-control path.

03

Requirements

Stable requirement IDs, testable language, source/owner, verification method and labelled state. Colour may assist scanning but never carry meaning alone.

Pre-flight review

A polished document is not production-ready until its decisions, evidence and operating state can be found without interpretation.

  1. 01Every claim points to evidence, a named assumption or an explicit future verification.
  2. 02Tables repeat their headers, preserve row meaning across pages and never rely on colour alone.
  3. 03Deliverables, owners, acceptance criteria, dates and change control are stated in testable language.
  4. 04Exported PDF text remains selectable, reading order is logical and links are descriptive.