System Readme

Plathera Industrial System

This brand system defines how Plathera appears, writes, names, diagrams, and proves seriousness for owner-side capital project teams.

What It Codifies

Sage/Builder rigor.
Owner-side buyer focus.
Category creation around the missing operating layer.
The three bottlenecks: access, context synthesis, admin offload.
Live program model, Project Graph, The Fabric, EPC Assistant, evidence traces, gate packets, and project registers.

System Thesis

Brand as visible project infrastructure.

The visual language is neutral record grounds, ruled grids, graphite panels, signal amber, labels, stamps, project packets, registers, and evidence traces.

Build Protocol

Start with the project record, not the layout. A Plathera surface should name the work scene, the artifact, the relationship, and the output before it reaches for imagery, token choices, or card structure.

Step	Operational Test	Acceptable Specificity
Scene	Where is the buyer making a decision?	Gate 3 review, variance review, claim posture, procurement recovery, turnover handoff.
Record	Which artifact anchors the claim?	RFI-118, SCH-W32, PO-7742, PKG-MEP-03, DEC-204, PCR-071, PERMIT-AQ-14.
Relationship	What does Plathera make inspectable?	RFI to drawing, change to milestone, risk to package, permit condition to field work, decision to evidence.
Output	What can the team act on?	Gate packet, evidence trace, constraint register, variance brief, handoff memo, decision log.

Current Homepage Rules

Rule	Guidance
Theme	Dark uses #131417. Light uses neutral #EFEFEF, not beige. Both behave like record surfaces.
Grid	The grid is full-page infrastructure: 32px minor lines at 1px, 160px major lines at 3px, subtle cursor glow.
Signal amber	Use amber for eyebrows, active/current state, table headers, diagram nodes, focus, and short emphasis.
Cards	Peer cards share one surface and vary number, eyebrow, title, and body color. Surface changes must encode status.
Type	Gear Wide may mark short strong emphasis, stamps, and chips; long records stay Chivo Mono or Arial.
Proof	Use source systems, named records, package codes, decision IDs, and evidence links before abstract capability language.

Source Audit

Source	New Counterpart	Strategic Treatment
README.md	README.md / index.html / readme.html	Governance preserved; system metaphor changed from terminal aesthetic to project-record infrastructure.
00-archetype-and-promise.md	00-archetype-and-promise.md	Sage/Creator becomes Sage/Builder; project truth becomes emotional center.
01-positioning.md	01-positioning.md	Category frame moves from cognitive infrastructure to infrastructure for capital project truth.
02-voice-tone.md	02-voice-tone.md	Operator-authored voice gains industrial/project-record nouns.
03-naming-architecture.md	03-naming-architecture.md	Product names organized around project artifacts and traceability.
07-ui-diagrams.md	07-ui-diagrams.md / .html	Diagrams become schematics, registers, packets, and trace cards.
04 / 05 / 06 HTML docs	04 / 05 / 06 HTML docs	Same coverage, new visual and strategic language.
tokens	tokens	Neutral dark/light record palette, signal amber, grid, spacing, and typography codified.
applications	applications	Homepage, deck, and LinkedIn templates rebuilt with grid canvas, signal accents, and status surfaces.
mockups	mockups	Product configuration and artifact-review examples moved into the brand system beside application templates.
Historical Operator Terminal territory	Industrial System	Rigor, amber cues, and manual discipline retained; numeric-first terminal framing replaced by named project records and capital-project proof.