Skip to main content
← BUILD 042PROGRAM ARCHIVE
DURABLE BUILD ARCHIVE / STRUCTURED PUBLIC · CERTIFICATION OPEN

BUILD 042
Give the AI a Real Job

An AI role becomes governable when purpose, responsibilities, prohibited actions, approved tools, human review, stopping, evaluation, ownership, and inherited controls are one inspectable contract.

QUESTIONWhat exactly is this AI role allowed to do, with which tools, reviews, evaluations, and stop conditions?
STRUCTURED PUBLIC BUILD ARCHIVE

Research, creation, decisions, audits and plans are publicly structured without claiming that every release gate is complete.

DURABLE-RECORD RULE

This page exists so the durable record does not depend on conversation history. Research, decisions, generated artifacts, audits, limitations, media metadata, plans and canonical source paths are retained here as part of the build itself. A listed repository path proves that an implementation record was retained; it does not independently support a real-world factual claim.

SOURCE-LINK AVAILABILITY

0 of 5 listed retained paths have a public reader link on this archive page. Unlinked paths remain named for traceability but are not represented as publicly inspectable evidence.

01 / RESEARCH + EVIDENCE

What informed the build

Agent Role Engine v1data/build-042-engine-v1.json

Versioned role, permission, review, stop, evaluation, owner, and inherited-control rules over a synthetic fixture.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
02 / CREATED

What exists because we built it

042-A Give the AI a Real Job

Adds write responsibility, blocks it without before-write review, repairs the role, and exports exact state.

Governed Agent Role Primitive

Reusable role infrastructure for multi-agent teams and workflow orchestration.

03 / ARCHITECTURE + DECISIONS

Why it works this way

Canon and lineage are frozen

Uses 012, 039, 040, 041; creates cap:042; direct consumers are 043 and 092.

Write is separately gated

Approved tool identity alone cannot authorize write responsibility without a before-write human review point.

Control records are concrete

The role requires versioned consequence, trace, stop, and ownership records.

Role readiness is not permission

ROLE READY does not establish authorization, competence, safe execution, valid tool behavior, or effective supervision.

04 / AUDIT + RELEASE

How the work was checked

Machine-readable archivedata/build-042-archive-v1.json

State-only replay and exact nonclaims.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Privacy/supportdata/build-042-privacy-support-v1.json

Synthetic browser-local role with no real permissions.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Freshness/performancedata/build-042-freshness-performance-v1.json

Versioned deterministic O(n) role inspection.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
Browser fixturestests/build042.spec.ts

Write gate, repair, export, 320px, and accessible topology.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
05 / PLANS + OPEN THREADS

What this build intentionally leaves forward

Independent release gates

Authenticated browser, physical-device/manual accessibility, hosted CI, role-governance expert review, and media certification remain separate.

Future consumers

043 and 092 consume cap:042.

06 / MEDIA

Take the social artifact with you

B-LINKEDIN / CANONICAL FILM

720×900 · 4:5 MP4 · 24 fps · silent-first

CURRENT VERIFIED MEDIA / 30-second film · 105.5 KB

FINAL PROPOSITION / Give the AI a bounded job.

SHA-256 e4bd7c7c3723a33977eafbd360e8adb254e6715f0040649548fd4fca86fc0214Reproducible from data/linkedin-film-specs-v1.json with scripts/render-linkedin-films.py. The website—not a chat attachment—is the canonical media source.
07 / CANONICAL SOURCE INVENTORY

The repository files that preserve the implementation record

apps/web/app/100-builds/042/a/RoleLab.tsxapps/web/app/100-builds/042/b/RoleTopology.tsxpackages/release/src/agent-role-engine.tsdata/build-042-engine-v1.jsondocs/builds/042/SPEC.mdtests/build042.spec.ts

These paths preserve the implementation record. Only items with an explicit public reader link are publicly inspectable here. A file path, working interface or internal engine is not independent support for a real-world claim; synthetic propositions and design reasoning remain labeled within the retained record.