Manual Intelligence Engine Method v1
data/build-004-engine-v1.jsonGoverned source schema, claim schema, verification contract, evidence-boundary invariants, and limitations.
BUILD 004
Manual Intelligence Engine
A research system should expose collection, provenance, source/claim separation, verification state, contradiction, uncertainty, and synthesis rules before any automation is allowed to hide them.
QUESTIONWhat has to be true before research deserves automation?
CERTIFIED PUBLIC BUILD ARCHIVE
The complete structured public archive is certified for this build.
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.
7 of 7 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.
What informed the build
Provenance upgrade
Issuer/author, publication/version, source date, checked/retrieval date, and relevant section/page were made explicit rather than buried in notes.
Technological-ceiling survey
Automatic retrieval, model synthesis/extraction, vector retrieval, truth scoring, and agentic research were considered and rejected for this cycle because they would automate the method before making it inspectable.
What exists because we built it
004-A Manual Intelligence Engine
Collection protocol → source register → claim verification queue → evidence-bounded intelligence brief.
004-B Intelligence Chain Story
Interactive RAW → COLLECT → SEPARATE → VERIFY → BRIEF visual master.
Local JSON research-record export
Preserves the working state without requiring an external service.
Public build record
Making, method, evidence, and limits.
Why it works this way
Verified requires a verification note
A claim cannot enter verified findings merely because a reviewer clicked a status.
Clearing the note demotes the claim
The system enforces its evidence boundary rather than relying on memory.
Contradiction/uncertainty remain visible
The brief is status-derived; unresolved states cannot be flattened into findings.
How the work was checked
004 acceptance matrix
data/build-004-acceptance-v1.jsonMachine-readable release gates and evidence basis.
004 artifact inventory
data/build-004-artifacts-v1.jsonA/B-Web/B-LinkedIn production state and media gate.
004 privacy/support
data/build-004-privacy-support-v1.jsonState handling, privacy boundary, and support assumptions.
004 freshness/performance
data/build-004-freshness-performance-v1.jsonNetwork/model dependencies, resilience, and performance record.
004 release record
docs/builds/004-release-record.mdDetailed release engineering and adversarial audit history.
004 LinkedIn production record
docs/builds/004-linkedin-production.mdFilm dimensions, runtime, checksum, sampled-frame QA, and remaining phone/platform QA.
What this build intentionally leaves forward
Automation comes later
004 creates the inspectable manual method that future retrieval/synthesis/agentic systems may inherit once their behavior can be governed.
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 · 331.8 KB
FINAL PROPOSITION / AUTOMATE THE METHOD ONLY AFTER YOU CAN SEE THE METHOD.
SHA-256 6524e75c433aa6d091e2b9f7883df335e9eace3b40e22bbea26fad0d3a22cf96Reproducible from data/linkedin-film-specs-v1.json with scripts/render-linkedin-films.py. The website—not a chat attachment—is the canonical media source.
The repository files that preserve the implementation record
apps/web/app/100-builds/004/a/ManualIntelligenceEngine.tsxapps/web/app/100-builds/004/b/IntelligenceChainStory.tsxdata/build-004-engine-v1.jsondata/build-004-acceptance-v1.jsondata/build-004-artifacts-v1.jsondata/build-004-privacy-support-v1.jsondata/build-004-freshness-performance-v1.jsondocs/builds/004-release-record.mddocs/builds/004-linkedin-production.mdtests/build004.spec.tstests/build004-story.spec.tstests/build004-routing.spec.tsThese 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.