01
Intent layer
The system starts by clarifying objectives, units, bounds, evidence level, and approval points before any state-changing action.
- IN
- Engineer goal + constraints
- OUT
- Reviewable plan
01Platform
A grammar for
engineering action.
PHYMER structures industrial intelligence as a sequence of explicit states—from intent and context to execution and evidence.
01.1Operating layers
02
Context layer
Local project information remains close to the work while governed capabilities contribute specialized methods and operating discipline.
- IN
- Local project state + domain knowledge
- OUT
- Grounded task context
03
Execution layer
Agent, Workflow, Skill, and Tool are distinct product objects. Each carries a clear purpose, interface, policy, and lifecycle.
- IN
- Approved plan + typed capability
- OUT
- Observable operation
04
Evidence layer
Completion is reported as an engineering state—not inflated into physical validation, global optimality, or production approval.
- IN
- Operation state + engineering result
- OUT
- Traceable decision support
01.2Capability objects
Separate the reasoning from the mechanism.
Clear object boundaries make capability delivery reviewable, updateable, and safer to operate.
01
Agent
A role that interprets intent and coordinates work.
02
Workflow
A versioned sequence of decisions, actions, and review gates.
03
Skill
Governed domain guidance delivered for a specific task.
04
Tool
A typed interface to software, data, or a physical-system operation.
01.3State, not theatre
Every operation has a legible state.
Long-running engineering work can wait, be steered, require approval, recover, fail, or complete. The interface should show the difference.
INT-01
Intent
Objective, constraints, evidence level
PLN-02
Plan
Tools, policy, resources, approval
EXE-03
Execute
Local capability invocation
VER-04
Verify
Results, provenance, human review
Architecture gives this grammar a place to run.
Continue to architecture