06 / INSIDE JEN

Many roles. One governed flow.

Specialized roles observe, understand, translate, build and protect. Dispatch coordinates their work within human and company permissions, and independent verification checks the claims that come back.

Choose a role below to see its part in the system.

06.1

The people define the boundary.

HUMAN / COMPANY AUTHORITY

Permissions and approvals

↓ intake within that authority

↕ requests and supported results

↕ separate assignment and report for each role

Verifier and Ethos also report through Dispatch. The layout groups responsibilities; it does not create a chain of workers commanding one another.

Dispatch

Coordinates the work.

Assigns bounded work to each role, receives its report and routes a separate verification assignment. It operates within existing human, company and policy authority; it does not create that authority.

06.2

What happens after “done”?

01
A role reports its work
The result returns to Dispatch with its evidence, limits and any uncertainty.
02
A separate check
Dispatch assigns independent verification of the underlying claim. The producer does not certify its own success.
03
The next permitted step
Results return to Dispatch. Further work or activation still requires the current authority for that exact action.

Explore the shared shell and testing foundation ↗

Athena

The human-facing guide.

Carries questions and requests into JEN through Dispatch and presents supported results naturally. She does not become the authority behind the system.

Wizard

Structured company setup.

Collects company goals, existing systems, constraints and permission choices for review. Consumer profile setup uses the consumer experience, not the company installation Wizard.

Dispatch

Coordinates the work.

Crawler

Observe the changing world.

Traverses authorized sources, records changes and preserves where information came from. Incomplete coverage stays visible. Crawler observes; Discovery interprets.

Discovery

Understand what is there.

Maps company systems, capabilities, gaps and the impact of change. Its findings return to Dispatch; it does not command Mechanical directly.

Translator Agent

Understand before building.

Deciphers code, formats and representations for construction requirements. It reports back through Dispatch. The runtime Translator has a separate job in established connections.

Builder

Create the candidate.

Builds implementation, shell and specialist candidates in an isolated development environment. Its work remains separate from installation into a company’s environment.

Mechanical

Connect and adapt the environment.

Installs, integrates, configures and repairs the authorized interface using eligible artifacts. It works under a bounded Dispatch assignment and reports the actual outcome.

Librarian

Preserve what JEN learns.

Maintains coherent knowledge and preserves completed proving journeys as authorized Footprints, including failures and limits. Reusable knowledge never becomes reusable permission.

Corporate specialist

Bring domain expertise.

A company can contribute requirements and domain knowledge for a specialized role. That role stays inside JEN’s frame, authority and evidence boundaries.

Verifier

Check the underlying claim.

A live system role as well as a development responsibility. Independently examines the result and evidence under a separate Dispatch assignment, then returns findings. It does not repair its own subject or authorize deployment.

Ethos

Watch health and integrity.

Observes behavior and health, reports findings, and performs containment or recovery only within authorized policy. Recovery must reconcile current reality and permission before work resumes.

Continue exploring / Tested foundations →

Step inside.

Many roles. One governed flow.

The people define the boundary.

Coordinates the work.

What happens after “done”?

A role reports its work

A separate check

The next permitted step

Explore the bigger picture.

A little piano jazz.