Naming Principle
- Name the project object being structured.
- Name the relationship being made visible.
- Name the decision, handoff, review, or packet the work supports.
- Use names that could appear in a project record.
- Describe method instead of magic.
Strategy 03
Naming Architecture
Plathera names systems by the capital-project work they make inspectable. Names should feel like controlled infrastructure components, not a portfolio of marketing inventions.
Master Brand
Plathera
Plathera is the company and the product. Use this single master brand until a product family is real enough to split. Industrial system, industrial operating layer, and record system are descriptive phrases, not capitalized sub-brands.
Descriptor System
Preferred: Infrastructure for capital project truth.
Alternate: The operating layer for capital projects.
Long-form: Plathera turns fragmented project systems into a live, defensible program model.
Product Architecture
| Product noun | Role | Naming rule |
|---|---|---|
| Plathera | Company and product. | Proper noun. Do not create unnecessary product-family names. |
| live program model | The market-facing center of the product: a connected representation of entities, evidence, decisions, risks, packages, milestones, cost, documents, correspondence, workflows, and status. | Lowercase in prose. Title case only in headings, labels, and tables. |
| Project Graph | The technical relationship layer beneath the live program model. | Capitalize when referring to Plathera's graph. Use for mechanism, architecture, technical sales, and investor material. |
| The Fabric | The ingestion, normalization, and linking layer. | Internal or technical-sales language. Do not market as a standalone feature. |
| EPC Assistant | The shipped assistant surface that acts against the structured program model. | Proper noun. Not AI Copilot, chatbot, helper, bot, or mascot. |
| workflow | A controlled project action the assistant can execute or support. | Name by function. Do not call workflows agents or assistants. |
Project Graph
Use Project Graph when the audience needs the relationship mechanism beneath the live program model.
EPC Assistant
The EPC Assistant asks questions of the program record, drafts reviews and briefs, assembles packets, checks evidence, summarizes changes, and routes the user to the relevant trace, register, or record.
It is one assistant surface, not a workforce of named personas.
Industrial Product Nouns
| Noun | Use for | Avoid |
|---|---|---|
| Record | The durable artifact or structured entry that proves what is known. | File, item, thing, content. |
| Packet | A bounded collection assembled for a gate, review, executive readout, or handoff. | Bundle, decklet, AI report. |
| Trace | The chain of evidence and relationships behind a claim, decision, risk, or constraint. | Insight, thread, AI finding. |
| Register | A controlled list with status, owner, evidence, and history. | Tracker, spreadsheet, list. |
| Brief | A concise output for review, leadership, or decision support. | Summary, AI output, auto-report. |
| Review | A structured inspection event or workflow. | Analysis, scan, smart review. |
| Handoff | Transfer of work, responsibility, or context between teams or phases. | Sync, share, collab. |
| Variance | A controlled gap between plan, evidence, and current state. | Issue, problem, surprise. |
Workflow Naming
Workflows are named after controlled project actions, not AI behaviors. Use the pattern [project function] workflow in prose.
| Workflow | Job | Rule |
|---|---|---|
| Catch-Up workflow | Gets a program leader current after time away. | Workflow, not agent. |
| Impact workflow | Assembles cross-domain implications when upstream state changes. | Replaces the separate Implication Agent idea. |
| Decision workflow | Ties decisions to program objects, evidence, and downstream effects. | Outputs may become Decision Records. |
| Reporting workflow | Prepares field notes, status packages, and leadership briefs for human editing. | Outputs may become Executive Review Packets. |
Weak To Better
| Weak | Better |
|---|---|
| AI Summary | Weekly Program Brief |
| Smart Review | Gate Packet Review |
| Ask AI | Query Project Record |
| Risk Bot | Constraint Trace |
| Document Analysis | Evidence Intake |
| Auto Report | Executive Review Packet |
| Project Assistant | EPC Assistant |
Status Naming
Visual Labels
Status words must explain any visual treatment. Color alone is not a naming system. A reader should understand the state if the page is printed in grayscale.
- Implemented can sit on a subdued surface.
- Current can use signal amber or a stronger rule.
- Forthcoming can use an inverse surface with sober copy.
- Evidence Missing, Blocked, and Ready for Gate need labels before color.
Content Architecture
Plathera publishing should feel like an extension of the project record.
| Content type | Description | Rule |
|---|---|---|
| Field Note | Short observation from inside capital delivery. | Use for regular public notes and LinkedIn essays. |
| Project Memo | Longer strategic or technical argument. | Use when the piece advances a thesis. |
| Architecture Brief | Product and systems essay. | Use for the live program model, Project Graph, Fabric, or EPC Assistant. |
| Gate Review | Investor or customer deck format. | Use for read-along artifacts, not generic slide decks. |
| Brief | Product output or marketing example of a product output. | Use only when the artifact has a bounded decision or review job. |
| Brand Book | Codified identity system. | Use for the public brand system. |
| Investor Memo | Capital-raise document. | Private, link-shared. |
| Hiring Memo | Role description and first-90-days expectation. | Use for recruiting surfaces. |
| Changelog | Product updates in plain English. | Use when there is actual shipped product change. |
Dos and Don’ts
| Do | Don’t |
|---|---|
| Name the object: Gate Packet, Evidence Trace, Constraint Register. | Name the magic: Smart AI Review, Instant Insight, Auto Genius. |
| Use nouns that could appear in a project record. | Use playful agent or mascot names. |
| Keep product architecture shallow. | Create a sub-brand for every capability. |
| Use EPC Assistant only for the assistant surface. | Call every workflow an assistant, agent, or bot. |
| Use Project Graph for the relationship layer. | Make Project Graph the whole product or public tagline. |
| Use status names that are auditable. | Use celebratory or vague UI states. |
Retired Names
- Virtual Agentic EPC Workforce as a product tagline.
- Agentic EPC Automation as a capability name.
- FTE Productivity Insights as a feature category.
- Governed Autonomy as a value proposition.
- Implication Agent as a separate marketed agent.
- Individual agent names that include Coordination.
- Master the Future of Agentic EPC as knowledge-hub framing.
- Ask me anything about Plathera as the homepage centerpiece.
- Any mascot, helper, copilot, bot, or fictional AI persona.
Decision Rule
Name the useful noun.
Before introducing a new name, classify the thing as a product layer, workflow, object, output, or status. Prefer industry language when it exists. If the name does not map to a record, packet, trace, register, decision, review, or handoff, make it more concrete. If it requires a footnote, implies AI theater, or will not survive eighteen months, keep it generic until the product earns the name.