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

BUILD 018
Institutional Friction Detector

An official process is also an experienced path. Waits, repeated loops, duplicate demands, dead ends, and ownerless states can make a valid institutional outcome inaccessible.

QUESTIONWhere is the institution making the path harder than it has to be?
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

Institutional Friction Engine v1data/build-018-engine-v1.json

Five observable friction classes, inherited workflow and handoff status, transparent score, and prioritized repair order.

RETAINED PATH LISTED · PUBLIC SOURCE LINK NOT AVAILABLE
OMB Circular A-11 Section 280

Grounds attention to public-facing service delivery, customer experience, measurement, and improvement.

OMB administrative-burden guidance

Grounds attention to time, learning, compliance, access, and psychological costs in public-benefit and service processes.

02 / CREATED

What exists because we built it

018-A Institutional Friction Detector

Detects bottlenecks, loops, dead ends, duplicate demands, and owner gaps, simulates repair, and exports locally.

Institutional Friction Finding and Repair Order v1

Reusable process signals for later escalation, implementation, and institutional-system builds.

03 / ARCHITECTURE + DECISIONS

Why it works this way

Builds 016 and 017 are concrete dependencies

The detector directly calls assessLegalWorkflow and assessRegulatedHandoffs before reporting local process friction.

The fixture contains a repairable defect

A duplicated evidence request, 96-hour wait, and three loops create visible hotspots; the simulation repairs only those bounded conditions.

Experienced burden is not reduced to one score

The score sorts observable signals while direct research with affected people remains necessary.

No compliance or eligibility claim

The engine cannot determine legal compliance, entitlement, institutional authority, or the full burden a person experiences.

04 / AUDIT + RELEASE

How the work was checked

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

Routes, lineage, privacy, deferred gates, and lifecycle.

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

Client-local operation and redesign boundary.

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

Official OMB sources and offline deterministic operation.

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

Hotspots, bounded repair, reset, export, lifecycle, 320px, and paired-visual coverage.

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

What this build intentionally leaves forward

Release path

Complete Vercel deployment and live browser verification; keep GitHub-hosted CI and media certification pending until Actions capacity returns.

Future consumers

019, 034, 048 and 093 consume cap:018.

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

FINAL PROPOSITION / FIND BOTTLENECKS, DEAD ENDS, REPEATED LOOPS AND AVOIDABLE BURDEN INSIDE INSTITUTIONAL PROCESSES.

SHA-256 6663a40c85030f9ef89cd9bad33c2f2a990b3824078bdaa1778cc29545546e03Reproducible 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/018/a/InstitutionalFrictionLab.tsxapps/web/app/100-builds/018/b/ProcessDrag.tsxpackages/release/src/decision-engines.tsdata/build-018-engine-v1.jsondata/build-018-archive-v1.jsondocs/builds/018/SPEC.mddocs/builds/018/ARCHIVE.mdtests/build018.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.