PROFESSIONALS
Software that knows when to refuse.
The dangerous kind of professional software is the kind that always answers. This layer declares what each role may do, and codifies the cases where the only correct output is a refusal.
- Roles with declared levels
- Refusal with a code
- A human can be mandatory
- No self-declared completion
Each claim tied to promoted code, not to a description.
A demonstration of the product direction. This layer is in active internal development.
WHAT IT IS FOR
The question is not what it can do. It is what it must not.
A tool that produces a confident answer for work that legally requires a licensed professional has not helped anyone. This layer makes the boundary part of the engine rather than part of the small print.
WHO IT IS FOR
Work where the order matters legally.
- Design and engineering practicesSteps that legally depend on prior documents.
- Teams with review obligationsApproval that is a real gate, not a checkbox.
- CoordinatorsWork that cannot silently skip a stage.
- Anyone answerable for a fileA record of what was required and when it arrived.
WHAT IS REAL TODAY
A role engine, with refusal built into it.
Every line below is sourced to code that is promoted and wired, not to a description of intent.
Professional roles as an engine
ImplementedA role is a real engine with its own modules and routes, not an instruction written at the top of a conversation.
Explicit levels of competence
ImplementedEvery role declares the level it is allowed to work at, from using a tool, to analysis, to citation, to producing a deliverable, to governed work.
A role is validated before it is used
ImplementedValidation happens first, as a step, not as an assumption.
Refusal is codified
ImplementedWhen a role cannot answer, the refusal carries a code. It is a defined outcome rather than a vague apology.
A licensed human can be mandatory
ImplementedSome work requires a licensed professional, and the engine says so itself and stops.
This is the strongest and the most honest claim on the page: the software refuses to be the professional.
A role cannot mark its own work as done
ImplementedA result reported by the role about itself is ignored. Completion is not self-declared.
Collaboration between roles
PartialMore than one role working on the same file.
In active development.
Execution reaching the file itself
DirectionAn approval that ends in the actual document rather than in a status change.
Not part of the canonical product.
Demonstrated: effect verified by a gate. Implemented: canonical code, wired. Partial: exists, with the limit stated. Direction: the goal, not a delivered capability.
BUILT ON THE ELDER
What the core contributes.
This layer is where the platform's authority model becomes visible as everyday professional work.
- IdentityWho is acting, established rather than declared.
- PermissionsThe second gate, independent of evidence.
- OrchestrationWorkflow order enforced by the platform.
- AuditWhat was required, what arrived, who approved.
WHAT IT DOES NOT DO
The limits, said plainly.
A gate is only worth something if its scope is honest.
- It does not certify work and does not replace professional responsibility.
- It enforces the order of a process; it does not judge the quality of the content.
- No legal or regulatory authorisation of any kind is claimed.
- Approval recorded here is not a legal signature.
- No client, project or document from real work is shown here.
STATE OF THE DEMONSTRATION
What this page is.
This page presents a layer where most of what is described already exists as working, verified code inside the platform.
It is not a commercial offer.
NEXT
If your work depends on the order being right.
Access begins with an evaluation of the process and the roles involved.