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

BUILD 041
Who Owns the AI Work?

AI work becomes governable when every declared tool, vendor, decision, and workflow has current accountable ownership, operational ownership, decision authority, and evidence.

QUESTIONWho is responsible for each AI tool, decision, vendor, and workflow—and where is accountability orphaned?
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

AI Work Ownership Engine v1data/build-041-engine-v1.json

Versioned ownership-role, evidence, review, expiry, orphan, conflict, and coverage rules over a synthetic fixture.

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

What exists because we built it

041-A Who Owns the AI Work?

Finds an orphaned workflow, reassigns accountable ownership and decision authority, and exports exact local state.

AI Work Ownership Primitive

Reusable accountability infrastructure for Build 042.

03 / ARCHITECTURE + DECISIONS

Why it works this way

Canon and lineage are repository-exact

Title, job, B-Web, uses 011/012/013/020, creates cap:041, and direct consumer 042 come from frozen tables.

Ownership roles remain distinct

Accountable owner, operational owner, and decision authority cannot silently collapse into one label.

Current records are required

Evidence identity, review date, expiry, unique ID, and valid evaluation date are visible gates.

Declared ownership is not legal responsibility

OWNED does not prove liability, actual authority, effective oversight, vendor control, complete discovery, or adoption.

04 / AUDIT + RELEASE

How the work was checked

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

Exact replay, derived fields, and nonclaims.

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

Synthetic browser-local topology.

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

Strict dated records and O(n) inspection.

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

Orphan repair, export, 320px, and accessible reassignment.

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, governance expert review, and media certification remain separate.

Future consumer

042 consumes cap:041.

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 · 106.7 KB

FINAL PROPOSITION / Ownership must follow every decision.

SHA-256 72a8a317023528caeca7aef177977cf4290ac8341e77223163e5388a5753432dReproducible 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/041/a/OwnershipLab.tsxapps/web/app/100-builds/041/b/OwnershipTopology.tsxpackages/release/src/ai-ownership-engine.tsdata/build-041-engine-v1.jsondocs/builds/041/SPEC.mdtests/build041.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.