Applications · Section 09
Applications overview
How the complete system behaves across business, technical and digital artifacts.
Application principle
One dominant field per page or sequence. Sapphire is the default. A workstream field may replace it on a clearly labelled divider or focused sequence.
Document matrix
Core colour establishes recognition; workstream colour provides local navigation; status colour communicates actual state.
| Artifact | Core | Workstream | Status |
|---|---|---|---|
| Proposal | Sapphire cover and navigation anchor | One family may lead a focused proposal; a multi-workstream proposal uses each family in its own section | Risks, milestones, decisions and delivery health only |
| Statement of work | Parchment and Nocturne, restrained | Optional and subtle; commercial and contractual pages stay core-neutral | Only where a genuine state is communicated |
| Technical requirements | Core neutral reading environment | Local, for system layers, requirement families or architecture regions | Validation, readiness, acceptance and risk |
| Presentation | Sapphire or Nocturne deck anchor | May own a divider or a coherent sequence; one dominant family per slide | Delivery and governance content |
| Website | Global navigation and structure | May identify service modules, case studies or page sections | Product and delivery pages |
| Dashboard and product UI | Neutral surfaces and structure | May categorise data or architecture | Operational state, always with text or shape |
| Case study and marketing | Sapphire default and unifying field | One family may become hero when the story belongs to it | Where outcomes are stated |
Artifact gallery
Illustrative applications show the rules in context. The examples demonstrate hierarchy and colour behaviour; no client, figure or screenshot is real.
Claims triage, from prototype to production
Sapphire anchors the cover. Each workstream owns its labelled divider, never the whole engagement.
Multi-workstream proposal. Core first; workstream navigation second.
One integration layer, nine source systems
A single workstream may lead a coherent focused proposal.
Focused proposal. Verdant owns the field because the engagement genuinely belongs to that workstream.
Deliverables and acceptance
Statement of work. Contractual pages stay restrained and core-neutral.
Non-functional requirements
p95 under 250 ms at 40 rps✓ Verified
Residency held in-region✓ Verified
Fallback path usable▲ In test
Technical requirements. Family and state are both labelled; colour is never the only signal.
Claims triage · production
Dashboard. Aqua distinguishes interaction from status through shape, placement, glyph and label.
The tool goes live on Monday. Here is what changes on your desk.
Three screens replaced by one. Nothing you have filed is lost.
Adoption communication. Plain language and a single workstream field.
Find your artifact
Use the focused guidance for the artifact you are producing.