What changed
Reviewed overview, A, B, engine/export, film/transcript and distribution as one claim surface.
Separated exact source concepts, RN synthesis, fictional fixture data and implementation.
Open the Decision
This is the public record behind the artifact: what changed, what another person can reuse, what supports the system, and what the build is not entitled to claim.
What travels
Keep synthetic records synthetic.
Reserve direct support for concepts at the exact locator.
Do not treat an interface, export or film as proof.
What supports it
External material is a bounded contextual anchor: W3C PROV Primer.
Interface rules remain RN synthesis and implementation.
What it cannot claim
Provenance supports representation of responsibility, derivation, revision and time. Ledger composition and reason remain RN synthesis; provenance does not prove truth, legality or decision quality.
This record does not validate effectiveness, safety, compliance, representativeness, cultural authority, professional suitability or outcomes.
External source locators
W3C PROV Primer →
Exact locator: §§2.3–2.6 and 2.8; worked examples §§3.3–3.6. Scope limit: Provenance supports representation of responsibility, derivation, revision and time. Ledger composition and reason remain RN synthesis; provenance does not prove truth, legality or decision quality.
VISUAL ASSET REVIEW
Hook image, source candidate, and release gates
The creator-owned cover remains live unless every external-candidate gate is explicitly complete. Disabled controls report canonical status; they do not imply an approval action occurred here.
Live creator-owned cover
Status: Release-eligible fallback
Credit: © RN Collins · RN Builds
Crop and claim boundary
Use the complete 720×900 frame. Do not crop the headline, build number, safe margins or prototype boundary.
This creator-owned opening frame supports only the visible build proposition and build identity. It is not documentary evidence and does not establish institutional endorsement, lived experience, product performance, safety, compliance, effectiveness, causation, community authority or outcome.
Official visual candidate
Disposition: CLEARED-NOT-SUBSTITUTED
CLEARED — exact document asset may be reused under the recorded public-domain/open-license terms, subject to the stated attribution, exclusion and no-endorsement conditions.
Production specification
Orientation/dimensions: responsive document; no intrinsic pixel dimensions; × . Exact HTML document; capture dimensions must be specified at production time.
Crop: Crop boundary: Document text only: title, W3C Note status line and Abstract; exclude W3C marks, editor block, navigation, figures, examples and footer.
Alt text: Official W3C PROV Primer document or guidance page, selected as contextual evidence for Build 020, Open the Decision.
Credit: Copyright © 2013 W3C®. Material reproduced from PROV Model Primer, https://www.w3.org/TR/prov-primer/, under the W3C Document License.
Claim boundary: Supports recognition of W3C PROV Primer and the limited source context adjacent to Build 020; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.
Final hook-image decision
RETAINED RN COVER · OFFICIAL CANDIDATE REVIEW-ONLY
PROV Primer is only indirect context for opening a decision record; retain the build-specific RN hook.
Rollback: The prior RN cover remains preserved at its canonical asset URL.
CANONICAL SEVEN-SLIDE PRODUCTION BLUEPRINT
Build-specific carousel plan
Cover: Open exact mapped asset →
- 1. Hook
A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.Visual, rights, and accessibility instructions
Use the complete RN-owned cover at /media/builds/020/build-020-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.
Claim boundary: This creator-owned opening frame supports only the visible build proposition and build identity. It is not documentary evidence and does not establish institutional endorsement, lived experience, product performance, safety, compliance, effectiveness, causation, community authority or outcome.
Accessibility: Slide 1 alt text must identify Build 020, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.
Rights: Creator-owned production asset; no third-party visual incorporated.
- 2. Problem
The problem: Open the Decision fails when the underlying decision, audience, or evidence boundary is left implicit.Visual, rights, and accessibility instructions
RN-owned problem framing: isolate the tension behind “A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.”. Use typography plus one simple contrast or decision fork; no stock people.
Claim boundary: RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.
Accessibility: Slide 2 alt text must identify Build 020, the problem function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.
Rights: Use RN-owned typography, diagrams, and verified prototype captures only.
- 3. System
The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.Visual, rights, and accessibility instructions
Show an RN-owned diagram or prototype view of the Open the Decision mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.
Claim boundary: RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.
Accessibility: Slide 3 alt text must identify Build 020, the system function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.
Rights: Use RN-owned typography, diagrams, and verified prototype captures only.
- 4. Evidence
Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.Visual, rights, and accessibility instructions
Use an RN-owned evidence-boundary card. The recognizable entity “W3C PROV Primer” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.
Claim boundary: Supports recognition of W3C PROV Primer and the limited source context adjacent to Build 020; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.
Accessibility: Slide 4 alt text must identify Build 020, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.
Rights: RN-owned design only; contextual source: https://www.w3.org/TR/prov-primer/; no third-party visual authorized.
- 5. Demo
Demo: walk through one bounded state change in the Build 020 prototype. Show the interaction or decision path, not an invented result.Visual, rights, and accessibility instructions
Use an authentic RN prototype/interface capture from Build 020, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.
Claim boundary: Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.
Accessibility: Slide 5 alt text must identify Build 020, the demo function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.
Rights: Use RN-owned typography, diagrams, and verified prototype captures only.
- 6. Implications
Implication: Open the Decision can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.Visual, rights, and accessibility instructions
Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.
Claim boundary: RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.
Accessibility: Slide 6 alt text must identify Build 020, the implications function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.
Rights: Use RN-owned typography, diagrams, and verified prototype captures only.
- 7. CTA + sources
Explore Build 020, Open the Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.Visual, rights, and accessibility instructions
Use a quiet RN-owned closing card with Build 020, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.
Claim boundary: RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.
Accessibility: Slide 7 alt text must identify Build 020, the cta + sources function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.
Rights: Use RN-owned typography, diagrams, and verified prototype captures only.
Platform repurposing
Instagram: Publish all seven 4:5 slides; keep credits and boundaries on-slide; write the supplied alt text manually.
LinkedIn: Export as an accessible seven-page PDF; preserve live links in the post copy and use the build dossier as the canonical source.
Reels/TikTok: Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.
Web/newsletter: Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation.
Download all 100 structured blueprints ↓ · Read production instructions →
Finished seven-slide production assets
All seven accessible 1200×1500 slides for this build are generated and included in the deterministic distribution packages. Metadata retains exact alt text, visual guidance, credit, source, rights, and claim boundaries.
- Slide 1: Hook →
- Slide 2: Problem →
- Slide 3: System →
- Slide 4: Evidence →
- Slide 5: Demo →
- Slide 6: Implications →
- Slide 7: CTA + sources →
Open carousel asset operations → · Open 700-slide inventory → · Read import instructions →
Download this build’s Canva batch ↓ · Download Instagram package ↓ · Download LinkedIn package ↓
Canva-ready distribution
This build’s current cover and complete metadata are included in the deterministic 100-cover handoff. The package preserves this dossier’s official/RN decision, source, rights, claim boundary, and rollback state.
Download the complete Canva-ready ZIP ↓ · Open package inventory → · Read import instructions →
How to read this record.
A public build record has four sections and they are ordered on purpose. Making is the narrative of what changed, written so that someone who was not there can follow the decisions in sequence. Method is the part meant to travel: the rules and structures another person could apply to a different problem in a different field. Evidence is what supports the system, stated as specifically as the underlying material allows. Limits close the record because they determine how far everything above them can be carried.
The reason limits come last is that they are the part most often left out, and a record without them is a marketing page with citations. Every claim in the sections above is bounded by what the final section says, and a reader who skips it will overstate what the build establishes. If you only have time for two sections, read Method and Limits: together they tell you what you could reuse and how far you could trust it.
Where external sources appear, each is given with an exact locator rather than a bare link, so the specific passage relied on can be checked instead of the whole document. A scope limit accompanies each one. That limit describes what the source was used for in this build, which is frequently narrower than what the source as a whole covers, and quoting the source for a broader claim than the scope allows would be a misuse of it even though the link resolves.
Language here is chosen to hold up under scrutiny rather than to sound confident. Where a review is complete, the record says so and names what the review covered. Where a review remains open, the record says that instead, and continues to say it until the work is done. A statement that something is a demonstration, a synthetic fixture or an unverified claim is a factual description of that artifact, and it stays on the page because removing it would make the surrounding claims read as stronger than the evidence supports.
Finally, this record documents one build among a hundred that are designed to inherit from each other. What Method describes is often the thing a later build depends on, so a record is worth reading alongside the lineage view rather than purely on its own. That is where the capability described here can be traced forward into whatever was built on top of it.