{ "schemaVersion": "1.0.0", "range": "001-100", "generatedAt": "2026-08-28", "policy": { "purpose": "Canonical editorial production blueprints; not proof of Canva construction, export, publication, performance, or endorsement.", "format": "Seven-slide 4:5 carousel at 1200×1500. Preserve a 96 px text-safe inset and sequential reading order.", "recognizableImagery": "Use the recorded live cover on slide 1. Elsewhere use only RN-owned interface/prototype views or the exact recorded official source under its rights and claim boundaries.", "accessibility": "Minimum 48 px body type at 1200×1500; WCAG AA contrast; never encode meaning by color alone; one reading-order heading; meaningful alt text; captions/transcript for motion.", "release": "Every slide requires editorial, accessibility, rights, claim-scope, mobile-legibility, and link review. Canva generation remains unauthorized until an actual Canva design record exists." }, "expected": { "records": 100, "slidesPerRecord": 7, "totalSlides": 700 }, "records": [ { "buildId": "001", "title": "Human Review Design Framework", "template": "RN Builds 4:5 / evidence-and-governance / Build 001", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-context/build-001-official-source-context.svg", "altText": "Official NIST AI 100-1 title-page text, selected as contextual evidence for Build 001, Human Review Design Framework. Production source-context derivative; not evidence of prototype performance or institutional endorsement.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/001/build-001-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Human Review Design Framework and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 001." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "HUMAN IN THE LOOP? That phrase hides the part that matters.", "The problem: Human Review Design Framework fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 001 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Review Design Framework can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 001, Human Review Design Framework: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "HUMAN IN THE LOOP? That phrase hides the part that matters.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-context/build-001-official-source-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 001, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST public information · no endorsement" }, { "slide": 2, "stage": "Problem", "copy": [ "HUMAN IN THE LOOP? That phrase hides the part that matters.", "The problem: Human Review Design Framework fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 001 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Review Design Framework can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 001, Human Review Design Framework: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Human Review Design Framework fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “HUMAN IN THE LOOP? That phrase hides the part that matters.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 001, 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." }, { "slide": 3, "stage": "System", "copy": [ "HUMAN IN THE LOOP? That phrase hides the part that matters.", "The problem: Human Review Design Framework fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 001 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Review Design Framework can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 001, Human Review Design Framework: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Human Review Design Framework mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 001, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "HUMAN IN THE LOOP? That phrase hides the part that matters.", "The problem: Human Review Design Framework fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 001 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Review Design Framework can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 001, Human Review Design Framework: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 001, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1. Republished courtesy of NIST. NIST public information · no endorsement" }, { "slide": 5, "stage": "Demo", "copy": [ "HUMAN IN THE LOOP? That phrase hides the part that matters.", "The problem: Human Review Design Framework fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 001 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Review Design Framework can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 001, Human Review Design Framework: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 001 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 001, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 001, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "HUMAN IN THE LOOP? That phrase hides the part that matters.", "The problem: Human Review Design Framework fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 001 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Review Design Framework can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 001, Human Review Design Framework: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Human Review Design Framework can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 001, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "HUMAN IN THE LOOP? That phrase hides the part that matters.", "The problem: Human Review Design Framework fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 001 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Review Design Framework can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 001, Human Review Design Framework: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 001, Human Review Design Framework: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 001, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 001, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "002", "title": "Multi-Audience Meaning Architecture", "template": "RN Builds 4:5 / evidence-and-governance / Build 002", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/replacement-production-covers/build-002-official-excerpt-cover.svg", "altText": "Official GOV.UK user-research guidance stating that teams must understand all kinds of users and write needs using words users recognise, shown as source context for Build 002.", "credit": "Contains public sector information licensed under the Open Government Licence v3.0. Source: GOV.UK Service Manual, Learning about users and their needs.", "sourceUrl": "https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs", "rollbackAssetUrl": "/media/builds/002/build-002-linkedin-poster.png" }, "recognizableEntity": { "label": "GOV.UK Learning about users and their needs", "type": "official government guidance", "relevance": "GOV.UK Learning about users and their needs is directly relevant to Multi-Audience Meaning Architecture and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that UK Government Digital Service / User research community endorses RN or Build 002." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "ONE IDEA. MANY AUDIENCES. Adaptation is useful only if the factual core survives.", "The problem: Multi-Audience Meaning Architecture fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK guidance: include all kinds of users and preserve words users recognise.", "Demo: walk through one bounded state change in the Build 002 prototype. Show the interaction or decision path, not an invented result.", "Implication: Multi-Audience Meaning Architecture can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 002, Multi-Audience Meaning Architecture: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "ONE IDEA. MANY AUDIENCES. Adaptation is useful only if the factual core survives.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/replacement-production-covers/build-002-official-excerpt-cover.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports the need to represent multiple audiences and preserve user-recognisable language; it does not validate RN’s architecture, prove outcomes or imply endorsement.", "accessibility": "Slide 1 alt text must identify Build 002, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "OGL v3.0 Crown-copyright text; logo and third-party material excluded." }, { "slide": 2, "stage": "Problem", "copy": [ "ONE IDEA. MANY AUDIENCES. Adaptation is useful only if the factual core survives.", "The problem: Multi-Audience Meaning Architecture fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK guidance: include all kinds of users and preserve words users recognise.", "Demo: walk through one bounded state change in the Build 002 prototype. Show the interaction or decision path, not an invented result.", "Implication: Multi-Audience Meaning Architecture can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 002, Multi-Audience Meaning Architecture: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Multi-Audience Meaning Architecture fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “ONE IDEA. MANY AUDIENCES. Adaptation is useful only if the factual core survives.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 002, 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." }, { "slide": 3, "stage": "System", "copy": [ "ONE IDEA. MANY AUDIENCES. Adaptation is useful only if the factual core survives.", "The problem: Multi-Audience Meaning Architecture fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK guidance: include all kinds of users and preserve words users recognise.", "Demo: walk through one bounded state change in the Build 002 prototype. Show the interaction or decision path, not an invented result.", "Implication: Multi-Audience Meaning Architecture can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 002, Multi-Audience Meaning Architecture: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Multi-Audience Meaning Architecture mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 002, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "ONE IDEA. MANY AUDIENCES. Adaptation is useful only if the factual core survives.", "The problem: Multi-Audience Meaning Architecture fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK guidance: include all kinds of users and preserve words users recognise.", "Demo: walk through one bounded state change in the Build 002 prototype. Show the interaction or decision path, not an invented result.", "Implication: Multi-Audience Meaning Architecture can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 002, Multi-Audience Meaning Architecture: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: GOV.UK guidance: include all kinds of users and preserve words users recognise.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports the need to represent multiple audiences and preserve user-recognisable language; it does not validate RN’s architecture, prove outcomes or imply endorsement.", "accessibility": "Slide 4 alt text must identify Build 002, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Contains public sector information licensed under the Open Government Licence v3.0. Source: GOV.UK Service Manual, Learning about users and their needs. OGL v3.0 Crown-copyright text; logo and third-party material excluded." }, { "slide": 5, "stage": "Demo", "copy": [ "ONE IDEA. MANY AUDIENCES. Adaptation is useful only if the factual core survives.", "The problem: Multi-Audience Meaning Architecture fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK guidance: include all kinds of users and preserve words users recognise.", "Demo: walk through one bounded state change in the Build 002 prototype. Show the interaction or decision path, not an invented result.", "Implication: Multi-Audience Meaning Architecture can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 002, Multi-Audience Meaning Architecture: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 002 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 002, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 002, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "ONE IDEA. MANY AUDIENCES. Adaptation is useful only if the factual core survives.", "The problem: Multi-Audience Meaning Architecture fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK guidance: include all kinds of users and preserve words users recognise.", "Demo: walk through one bounded state change in the Build 002 prototype. Show the interaction or decision path, not an invented result.", "Implication: Multi-Audience Meaning Architecture can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 002, Multi-Audience Meaning Architecture: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Multi-Audience Meaning Architecture can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 002, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "ONE IDEA. MANY AUDIENCES. Adaptation is useful only if the factual core survives.", "The problem: Multi-Audience Meaning Architecture fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK guidance: include all kinds of users and preserve words users recognise.", "Demo: walk through one bounded state change in the Build 002 prototype. Show the interaction or decision path, not an invented result.", "Implication: Multi-Audience Meaning Architecture can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 002, Multi-Audience Meaning Architecture: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 002, Multi-Audience Meaning Architecture: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 002, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 002, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "003", "title": "Unserved Decision Discovery", "template": "RN Builds 4:5 / evidence-and-governance / Build 003", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-variants/build-003-official-context.svg", "altText": "Build 003, Unserved Decision Discovery. Official GOV.UK Learning about users and their needs document or guidance page, selected as contextual evidence for Build 003, Unserved Decision Discovery.", "credit": "Contains public sector information licensed under the Open Government Licence v3.0. Source: GOV.UK Service Manual, Learning about users and their needs.", "sourceUrl": "https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs", "rollbackAssetUrl": "/media/builds/003/build-003-linkedin-poster.png" }, "recognizableEntity": { "label": "GOV.UK Learning about users and their needs", "type": "official government guidance", "relevance": "GOV.UK Learning about users and their needs is directly relevant to Unserved Decision Discovery and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that UK Government Digital Service / User research community endorses RN or Build 003." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THEY HAVE INFORMATION. But they still cannot reliably decide what to do.", "The problem: Unserved Decision Discovery fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on learning about users and their needs.", "Demo: walk through one bounded state change in the Build 003 prototype. Show the interaction or decision path, not an invented result.", "Implication: Unserved Decision Discovery can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 003, Unserved Decision Discovery: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THEY HAVE INFORMATION. But they still cannot reliably decide what to do.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-variants/build-003-official-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of GOV.UK Learning about users and their needs and the limited source context adjacent to Build 003; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 003, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Open Government Licence v3.0 · Crown copyright source" }, { "slide": 2, "stage": "Problem", "copy": [ "THEY HAVE INFORMATION. But they still cannot reliably decide what to do.", "The problem: Unserved Decision Discovery fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on learning about users and their needs.", "Demo: walk through one bounded state change in the Build 003 prototype. Show the interaction or decision path, not an invented result.", "Implication: Unserved Decision Discovery can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 003, Unserved Decision Discovery: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Unserved Decision Discovery fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THEY HAVE INFORMATION. But they still cannot reliably decide what to do.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 003, 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." }, { "slide": 3, "stage": "System", "copy": [ "THEY HAVE INFORMATION. But they still cannot reliably decide what to do.", "The problem: Unserved Decision Discovery fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on learning about users and their needs.", "Demo: walk through one bounded state change in the Build 003 prototype. Show the interaction or decision path, not an invented result.", "Implication: Unserved Decision Discovery can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 003, Unserved Decision Discovery: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Unserved Decision Discovery mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 003, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THEY HAVE INFORMATION. But they still cannot reliably decide what to do.", "The problem: Unserved Decision Discovery fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on learning about users and their needs.", "Demo: walk through one bounded state change in the Build 003 prototype. Show the interaction or decision path, not an invented result.", "Implication: Unserved Decision Discovery can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 003, Unserved Decision Discovery: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: GOV.UK Service Manual guidance on learning about users and their needs.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of GOV.UK Learning about users and their needs and the limited source context adjacent to Build 003; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 003, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Contains public sector information licensed under the Open Government Licence v3.0. Source: GOV.UK Service Manual, Learning about users and their needs. Open Government Licence v3.0 · Crown copyright source" }, { "slide": 5, "stage": "Demo", "copy": [ "THEY HAVE INFORMATION. But they still cannot reliably decide what to do.", "The problem: Unserved Decision Discovery fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on learning about users and their needs.", "Demo: walk through one bounded state change in the Build 003 prototype. Show the interaction or decision path, not an invented result.", "Implication: Unserved Decision Discovery can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 003, Unserved Decision Discovery: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 003 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 003, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 003, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THEY HAVE INFORMATION. But they still cannot reliably decide what to do.", "The problem: Unserved Decision Discovery fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on learning about users and their needs.", "Demo: walk through one bounded state change in the Build 003 prototype. Show the interaction or decision path, not an invented result.", "Implication: Unserved Decision Discovery can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 003, Unserved Decision Discovery: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Unserved Decision Discovery can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 003, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THEY HAVE INFORMATION. But they still cannot reliably decide what to do.", "The problem: Unserved Decision Discovery fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on learning about users and their needs.", "Demo: walk through one bounded state change in the Build 003 prototype. Show the interaction or decision path, not an invented result.", "Implication: Unserved Decision Discovery can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 003, Unserved Decision Discovery: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 003, Unserved Decision Discovery: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 003, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 003, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "004", "title": "Before the Automation", "template": "RN Builds 4:5 / evidence-and-governance / Build 004", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-variants/build-004-official-context.svg", "altText": "Build 004, Before the Automation. Official NIST AI RMF Playbook document or guidance page, selected as contextual evidence for Build 004, Before the Automation.", "credit": "Source: National Institute of Standards and Technology, NIST AI RMF Playbook. Republished courtesy of NIST.", "sourceUrl": "https://www.nist.gov/itl/ai-risk-management-framework/nist-ai-rmf-playbook", "rollbackAssetUrl": "/media/builds/004/build-004-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI RMF Playbook", "type": "official government guidance", "relevance": "NIST AI RMF Playbook is directly relevant to Before the Automation and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 004." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A PILE OF SOURCES IS NOT INTELLIGENCE. The transformation happens through explicit gates.", "The problem: Before the Automation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The official NIST AI RMF Playbook, shown as automation-governance context.", "Demo: walk through one bounded state change in the Build 004 prototype. Show the interaction or decision path, not an invented result.", "Implication: Before the Automation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 004, Before the Automation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A PILE OF SOURCES IS NOT INTELLIGENCE. The transformation happens through explicit gates.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-variants/build-004-official-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of NIST AI RMF Playbook and the limited source context adjacent to Build 004; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 004, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Official NIST public information · Republished courtesy of NIST" }, { "slide": 2, "stage": "Problem", "copy": [ "A PILE OF SOURCES IS NOT INTELLIGENCE. The transformation happens through explicit gates.", "The problem: Before the Automation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The official NIST AI RMF Playbook, shown as automation-governance context.", "Demo: walk through one bounded state change in the Build 004 prototype. Show the interaction or decision path, not an invented result.", "Implication: Before the Automation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 004, Before the Automation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Before the Automation fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A PILE OF SOURCES IS NOT INTELLIGENCE. The transformation happens through explicit gates.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 004, 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." }, { "slide": 3, "stage": "System", "copy": [ "A PILE OF SOURCES IS NOT INTELLIGENCE. The transformation happens through explicit gates.", "The problem: Before the Automation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The official NIST AI RMF Playbook, shown as automation-governance context.", "Demo: walk through one bounded state change in the Build 004 prototype. Show the interaction or decision path, not an invented result.", "Implication: Before the Automation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 004, Before the Automation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Before the Automation mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 004, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A PILE OF SOURCES IS NOT INTELLIGENCE. The transformation happens through explicit gates.", "The problem: Before the Automation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The official NIST AI RMF Playbook, shown as automation-governance context.", "Demo: walk through one bounded state change in the Build 004 prototype. Show the interaction or decision path, not an invented result.", "Implication: Before the Automation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 004, Before the Automation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: The official NIST AI RMF Playbook, shown as automation-governance context.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.nist.gov/itl/ai-risk-management-framework/nist-ai-rmf-playbook; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of NIST AI RMF Playbook and the limited source context adjacent to Build 004; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 004, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Source: National Institute of Standards and Technology, NIST AI RMF Playbook. Republished courtesy of NIST. Official NIST public information · Republished courtesy of NIST" }, { "slide": 5, "stage": "Demo", "copy": [ "A PILE OF SOURCES IS NOT INTELLIGENCE. The transformation happens through explicit gates.", "The problem: Before the Automation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The official NIST AI RMF Playbook, shown as automation-governance context.", "Demo: walk through one bounded state change in the Build 004 prototype. Show the interaction or decision path, not an invented result.", "Implication: Before the Automation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 004, Before the Automation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 004 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 004, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 004, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A PILE OF SOURCES IS NOT INTELLIGENCE. The transformation happens through explicit gates.", "The problem: Before the Automation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The official NIST AI RMF Playbook, shown as automation-governance context.", "Demo: walk through one bounded state change in the Build 004 prototype. Show the interaction or decision path, not an invented result.", "Implication: Before the Automation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 004, Before the Automation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Before the Automation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 004, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A PILE OF SOURCES IS NOT INTELLIGENCE. The transformation happens through explicit gates.", "The problem: Before the Automation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The official NIST AI RMF Playbook, shown as automation-governance context.", "Demo: walk through one bounded state change in the Build 004 prototype. Show the interaction or decision path, not an invented result.", "Implication: Before the Automation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 004, Before the Automation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 004, Before the Automation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 004, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 004, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "005", "title": "Service Path Split", "template": "RN Builds 4:5 / evidence-and-governance / Build 005", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-variants/build-005-official-context.svg", "altText": "Build 005, Service Path Split. Official GOV.UK Service Standard document or guidance page, selected as contextual evidence for Build 005, Service Path Split.", "credit": "Contains public sector information licensed under the Open Government Licence v3.0. Source: UK Government Digital Service, GOV.UK Service Standard.", "sourceUrl": "https://www.gov.uk/service-manual/service-standard", "rollbackAssetUrl": "/media/builds/005/build-005-linkedin-poster.png" }, "recognizableEntity": { "label": "GOV.UK Service Standard", "type": "official government guidance", "relevance": "GOV.UK Service Standard is directly relevant to Service Path Split and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that UK Government Digital Service endorses RN or Build 005." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "DON’T AUTOMATE THE SERVICE. Separate the steps first.", "The problem: Service Path Split fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 005 prototype. Show the interaction or decision path, not an invented result.", "Implication: Service Path Split can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 005, Service Path Split: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "DON’T AUTOMATE THE SERVICE. Separate the steps first.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-variants/build-005-official-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of GOV.UK Service Standard and the limited source context adjacent to Build 005; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 005, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Open Government Licence v3.0 · Crown copyright source" }, { "slide": 2, "stage": "Problem", "copy": [ "DON’T AUTOMATE THE SERVICE. Separate the steps first.", "The problem: Service Path Split fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 005 prototype. Show the interaction or decision path, not an invented result.", "Implication: Service Path Split can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 005, Service Path Split: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Service Path Split fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “DON’T AUTOMATE THE SERVICE. Separate the steps first.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 005, 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." }, { "slide": 3, "stage": "System", "copy": [ "DON’T AUTOMATE THE SERVICE. Separate the steps first.", "The problem: Service Path Split fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 005 prototype. Show the interaction or decision path, not an invented result.", "Implication: Service Path Split can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 005, Service Path Split: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Service Path Split mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 005, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "DON’T AUTOMATE THE SERVICE. Separate the steps first.", "The problem: Service Path Split fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 005 prototype. Show the interaction or decision path, not an invented result.", "Implication: Service Path Split can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 005, Service Path Split: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.gov.uk/service-manual/service-standard; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of GOV.UK Service Standard and the limited source context adjacent to Build 005; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 005, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Contains public sector information licensed under the Open Government Licence v3.0. Source: UK Government Digital Service, GOV.UK Service Standard. Open Government Licence v3.0 · Crown copyright source" }, { "slide": 5, "stage": "Demo", "copy": [ "DON’T AUTOMATE THE SERVICE. Separate the steps first.", "The problem: Service Path Split fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 005 prototype. Show the interaction or decision path, not an invented result.", "Implication: Service Path Split can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 005, Service Path Split: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 005 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 005, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 005, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "DON’T AUTOMATE THE SERVICE. Separate the steps first.", "The problem: Service Path Split fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 005 prototype. Show the interaction or decision path, not an invented result.", "Implication: Service Path Split can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 005, Service Path Split: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Service Path Split can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 005, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "DON’T AUTOMATE THE SERVICE. Separate the steps first.", "The problem: Service Path Split fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 005 prototype. Show the interaction or decision path, not an invented result.", "Implication: Service Path Split can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 005, Service Path Split: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 005, Service Path Split: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 005, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 005, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "006", "title": "Form Gate Field", "template": "RN Builds 4:5 / evidence-and-governance / Build 006", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-variants/build-006-official-context.svg", "altText": "Build 006, Form Gate Field. Official GOV.UK Assisted digital support document or guidance page, selected as contextual evidence for Build 006, Form Gate Field.", "credit": "Contains public sector information licensed under the Open Government Licence v3.0. Source: GOV.UK Service Manual, Assisted digital support.", "sourceUrl": "https://www.gov.uk/service-manual/assisted-digital/", "rollbackAssetUrl": "/media/builds/006/build-006-linkedin-poster.png" }, "recognizableEntity": { "label": "GOV.UK Assisted digital support", "type": "official government guidance", "relevance": "GOV.UK Assisted digital support is directly relevant to Form Gate Field and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that UK Government Digital Service / Assisted digital and digital take-up community endorses RN or Build 006." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "SOFTWARE IS NOT THE DEFAULT. It is one form the problem may—or may not—earn.", "The problem: Form Gate Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on assisted digital support.", "Demo: walk through one bounded state change in the Build 006 prototype. Show the interaction or decision path, not an invented result.", "Implication: Form Gate Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 006, Form Gate Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "SOFTWARE IS NOT THE DEFAULT. It is one form the problem may—or may not—earn.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-variants/build-006-official-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of GOV.UK Assisted digital support and the limited source context adjacent to Build 006; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 006, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Open Government Licence v3.0 · Crown copyright source" }, { "slide": 2, "stage": "Problem", "copy": [ "SOFTWARE IS NOT THE DEFAULT. It is one form the problem may—or may not—earn.", "The problem: Form Gate Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on assisted digital support.", "Demo: walk through one bounded state change in the Build 006 prototype. Show the interaction or decision path, not an invented result.", "Implication: Form Gate Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 006, Form Gate Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Form Gate Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “SOFTWARE IS NOT THE DEFAULT. It is one form the problem may—or may not—earn.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 006, 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." }, { "slide": 3, "stage": "System", "copy": [ "SOFTWARE IS NOT THE DEFAULT. It is one form the problem may—or may not—earn.", "The problem: Form Gate Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on assisted digital support.", "Demo: walk through one bounded state change in the Build 006 prototype. Show the interaction or decision path, not an invented result.", "Implication: Form Gate Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 006, Form Gate Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Form Gate Field mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 006, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "SOFTWARE IS NOT THE DEFAULT. It is one form the problem may—or may not—earn.", "The problem: Form Gate Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on assisted digital support.", "Demo: walk through one bounded state change in the Build 006 prototype. Show the interaction or decision path, not an invented result.", "Implication: Form Gate Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 006, Form Gate Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: GOV.UK Service Manual guidance on assisted digital support.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.gov.uk/service-manual/assisted-digital/; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of GOV.UK Assisted digital support and the limited source context adjacent to Build 006; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 006, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Contains public sector information licensed under the Open Government Licence v3.0. Source: GOV.UK Service Manual, Assisted digital support. Open Government Licence v3.0 · Crown copyright source" }, { "slide": 5, "stage": "Demo", "copy": [ "SOFTWARE IS NOT THE DEFAULT. It is one form the problem may—or may not—earn.", "The problem: Form Gate Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on assisted digital support.", "Demo: walk through one bounded state change in the Build 006 prototype. Show the interaction or decision path, not an invented result.", "Implication: Form Gate Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 006, Form Gate Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 006 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 006, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 006, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "SOFTWARE IS NOT THE DEFAULT. It is one form the problem may—or may not—earn.", "The problem: Form Gate Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on assisted digital support.", "Demo: walk through one bounded state change in the Build 006 prototype. Show the interaction or decision path, not an invented result.", "Implication: Form Gate Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 006, Form Gate Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Form Gate Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 006, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "SOFTWARE IS NOT THE DEFAULT. It is one form the problem may—or may not—earn.", "The problem: Form Gate Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: GOV.UK Service Manual guidance on assisted digital support.", "Demo: walk through one bounded state change in the Build 006 prototype. Show the interaction or decision path, not an invented result.", "Implication: Form Gate Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 006, Form Gate Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 006, Form Gate Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 006, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 006, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "007", "title": "The Product That Learns", "template": "RN Builds 4:5 / evidence-and-governance / Build 007", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/replacement-production-covers/build-007-official-excerpt-cover.svg", "altText": "Official NIST AI RMF GOVERN 5 excerpt describing a governed feedback loop that incorporates adjudicated external feedback into AI-system design and implementation.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 24. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/007/build-007-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to The Product That Learns and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 007." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THE PRODUCT SHIPS. But shipping is one-way. Collection alone does not make a product learn.", "The problem: The Product That Learns fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 5: external feedback is collected, adjudicated and incorporated into system design and implementation.", "Demo: walk through one bounded state change in the Build 007 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Product That Learns can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 007, The Product That Learns: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THE PRODUCT SHIPS. But shipping is one-way. Collection alone does not make a product learn.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/replacement-production-covers/build-007-official-excerpt-cover.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports a governed product-learning feedback loop; it does not show that Build 007 implements NIST, learns correctly or improves outcomes.", "accessibility": "Slide 1 alt text must identify Build 007, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 2, "stage": "Problem", "copy": [ "THE PRODUCT SHIPS. But shipping is one-way. Collection alone does not make a product learn.", "The problem: The Product That Learns fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 5: external feedback is collected, adjudicated and incorporated into system design and implementation.", "Demo: walk through one bounded state change in the Build 007 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Product That Learns can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 007, The Product That Learns: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The Product That Learns fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THE PRODUCT SHIPS. But shipping is one-way. Collection alone does not make a product learn.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 007, 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." }, { "slide": 3, "stage": "System", "copy": [ "THE PRODUCT SHIPS. But shipping is one-way. Collection alone does not make a product learn.", "The problem: The Product That Learns fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 5: external feedback is collected, adjudicated and incorporated into system design and implementation.", "Demo: walk through one bounded state change in the Build 007 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Product That Learns can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 007, The Product That Learns: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Product That Learns mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 007, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THE PRODUCT SHIPS. But shipping is one-way. Collection alone does not make a product learn.", "The problem: The Product That Learns fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 5: external feedback is collected, adjudicated and incorporated into system design and implementation.", "Demo: walk through one bounded state change in the Build 007 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Product That Learns can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 007, The Product That Learns: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: NIST AI RMF GOVERN 5: external feedback is collected, adjudicated and incorporated into system design and implementation.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports a governed product-learning feedback loop; it does not show that Build 007 implements NIST, learns correctly or improves outcomes.", "accessibility": "Slide 4 alt text must identify Build 007, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 24. Republished courtesy of NIST. NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 5, "stage": "Demo", "copy": [ "THE PRODUCT SHIPS. But shipping is one-way. Collection alone does not make a product learn.", "The problem: The Product That Learns fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 5: external feedback is collected, adjudicated and incorporated into system design and implementation.", "Demo: walk through one bounded state change in the Build 007 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Product That Learns can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 007, The Product That Learns: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 007 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 007, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 007, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THE PRODUCT SHIPS. But shipping is one-way. Collection alone does not make a product learn.", "The problem: The Product That Learns fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 5: external feedback is collected, adjudicated and incorporated into system design and implementation.", "Demo: walk through one bounded state change in the Build 007 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Product That Learns can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 007, The Product That Learns: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The Product That Learns can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 007, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THE PRODUCT SHIPS. But shipping is one-way. Collection alone does not make a product learn.", "The problem: The Product That Learns fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 5: external feedback is collected, adjudicated and incorporated into system design and implementation.", "Demo: walk through one bounded state change in the Build 007 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Product That Learns can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 007, The Product That Learns: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 007, The Product That Learns: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 007, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 007, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "008", "title": "Data Is Not a Decision", "template": "RN Builds 4:5 / evidence-and-governance / Build 008", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/replacement-production-covers/build-008-official-excerpt-cover.svg", "altText": "Official NIST AI RMF MAP 2.2 excerpt requiring documentation of system knowledge limits and how output may be used and overseen by humans making decisions.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 26. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/008/build-008-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Data Is Not a Decision and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 008." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A WALL OF CHARTS. More information is visible. The decision is still missing.", "The problem: Data Is Not a Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MAP 2.2 distinguishes system output from the human decisions and subsequent actions it informs.", "Demo: walk through one bounded state change in the Build 008 prototype. Show the interaction or decision path, not an invented result.", "Implication: Data Is Not a Decision can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 008, Data Is Not a Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A WALL OF CHARTS. More information is visible. The decision is still missing.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/replacement-production-covers/build-008-official-excerpt-cover.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports separating output from decision and documenting human use and oversight; it does not prove the Build 008 interface produces correct decisions.", "accessibility": "Slide 1 alt text must identify Build 008, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 2, "stage": "Problem", "copy": [ "A WALL OF CHARTS. More information is visible. The decision is still missing.", "The problem: Data Is Not a Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MAP 2.2 distinguishes system output from the human decisions and subsequent actions it informs.", "Demo: walk through one bounded state change in the Build 008 prototype. Show the interaction or decision path, not an invented result.", "Implication: Data Is Not a Decision can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 008, Data Is Not a Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Data Is Not a Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A WALL OF CHARTS. More information is visible. The decision is still missing.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 008, 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." }, { "slide": 3, "stage": "System", "copy": [ "A WALL OF CHARTS. More information is visible. The decision is still missing.", "The problem: Data Is Not a Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MAP 2.2 distinguishes system output from the human decisions and subsequent actions it informs.", "Demo: walk through one bounded state change in the Build 008 prototype. Show the interaction or decision path, not an invented result.", "Implication: Data Is Not a Decision can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 008, Data Is Not a Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Data Is Not a Decision mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 008, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A WALL OF CHARTS. More information is visible. The decision is still missing.", "The problem: Data Is Not a Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MAP 2.2 distinguishes system output from the human decisions and subsequent actions it informs.", "Demo: walk through one bounded state change in the Build 008 prototype. Show the interaction or decision path, not an invented result.", "Implication: Data Is Not a Decision can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 008, Data Is Not a Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: NIST AI RMF MAP 2.2 distinguishes system output from the human decisions and subsequent actions it informs.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports separating output from decision and documenting human use and oversight; it does not prove the Build 008 interface produces correct decisions.", "accessibility": "Slide 4 alt text must identify Build 008, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 26. Republished courtesy of NIST. NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 5, "stage": "Demo", "copy": [ "A WALL OF CHARTS. More information is visible. The decision is still missing.", "The problem: Data Is Not a Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MAP 2.2 distinguishes system output from the human decisions and subsequent actions it informs.", "Demo: walk through one bounded state change in the Build 008 prototype. Show the interaction or decision path, not an invented result.", "Implication: Data Is Not a Decision can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 008, Data Is Not a Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 008 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 008, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 008, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A WALL OF CHARTS. More information is visible. The decision is still missing.", "The problem: Data Is Not a Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MAP 2.2 distinguishes system output from the human decisions and subsequent actions it informs.", "Demo: walk through one bounded state change in the Build 008 prototype. Show the interaction or decision path, not an invented result.", "Implication: Data Is Not a Decision can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 008, Data Is Not a Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Data Is Not a Decision can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 008, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A WALL OF CHARTS. More information is visible. The decision is still missing.", "The problem: Data Is Not a Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MAP 2.2 distinguishes system output from the human decisions and subsequent actions it informs.", "Demo: walk through one bounded state change in the Build 008 prototype. Show the interaction or decision path, not an invented result.", "Implication: Data Is Not a Decision can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 008, Data Is Not a Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 008, Data Is Not a Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 008, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 008, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "009", "title": "Transfer Is a Place Question", "template": "RN Builds 4:5 / evidence-and-governance / Build 009", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/009/build-009-linkedin-poster.png", "altText": "Build 009, Transfer Is a Place Question. Creator-owned 4:5 typographic opening frame. Visible text: “IT WORKED SOMEWHERE ELSE. That does not mean it can work here.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Transfer Is a Place Question and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 009." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "IT WORKED SOMEWHERE ELSE. That does not mean it can work here.", "The problem: Transfer Is a Place Question fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 009 prototype. Show the interaction or decision path, not an invented result.", "Implication: Transfer Is a Place Question can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 009, Transfer Is a Place Question: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "IT WORKED SOMEWHERE ELSE. That does not mean it can work here.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/009/build-009-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 009, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "IT WORKED SOMEWHERE ELSE. That does not mean it can work here.", "The problem: Transfer Is a Place Question fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 009 prototype. Show the interaction or decision path, not an invented result.", "Implication: Transfer Is a Place Question can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 009, Transfer Is a Place Question: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Transfer Is a Place Question fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “IT WORKED SOMEWHERE ELSE. That does not mean it can work here.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 009, 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." }, { "slide": 3, "stage": "System", "copy": [ "IT WORKED SOMEWHERE ELSE. That does not mean it can work here.", "The problem: Transfer Is a Place Question fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 009 prototype. Show the interaction or decision path, not an invented result.", "Implication: Transfer Is a Place Question can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 009, Transfer Is a Place Question: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Transfer Is a Place Question mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 009, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "IT WORKED SOMEWHERE ELSE. That does not mean it can work here.", "The problem: Transfer Is a Place Question fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 009 prototype. Show the interaction or decision path, not an invented result.", "Implication: Transfer Is a Place Question can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 009, Transfer Is a Place Question: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST AI Risk Management Framework 1.0” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Supports recognition of NIST AI Risk Management Framework 1.0 and the limited source context adjacent to Build 009; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 009, 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://doi.org/10.6028/NIST.AI.100-1; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "IT WORKED SOMEWHERE ELSE. That does not mean it can work here.", "The problem: Transfer Is a Place Question fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 009 prototype. Show the interaction or decision path, not an invented result.", "Implication: Transfer Is a Place Question can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 009, Transfer Is a Place Question: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 009 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 009, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 009, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "IT WORKED SOMEWHERE ELSE. That does not mean it can work here.", "The problem: Transfer Is a Place Question fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 009 prototype. Show the interaction or decision path, not an invented result.", "Implication: Transfer Is a Place Question can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 009, Transfer Is a Place Question: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Transfer Is a Place Question can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 009, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "IT WORKED SOMEWHERE ELSE. That does not mean it can work here.", "The problem: Transfer Is a Place Question fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 009 prototype. Show the interaction or decision path, not an invented result.", "Implication: Transfer Is a Place Question can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 009, Transfer Is a Place Question: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 009, Transfer Is a Place Question: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 009, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 009, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "010", "title": "From Words to Structure", "template": "RN Builds 4:5 / evidence-and-governance / Build 010", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/source-excerpts/build-010-source-excerpt-hold.svg", "altText": "Sequential text excerpt containing the title, 20 July 2017 Recommendation status, and opening abstract sentences of the official W3C SHACL specification.", "credit": "Copyright © 2017 W3C®. Excerpt under the W3C Document License linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2015/doc-license", "sourceUrl": "https://www.w3.org/TR/2017/REC-shacl-20170720/", "rollbackAssetUrl": "/media/builds/010/build-010-linkedin-poster.png" }, "recognizableEntity": { "label": "W3C SHACL Recommendation", "type": "official web standard", "relevance": "W3C SHACL Recommendation is directly relevant to From Words to Structure and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that World Wide Web Consortium endorses RN or Build 010." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THE IDEA SOUNDS CLEAR. Until two people mean different things by the same noun.", "The problem: From Words to Structure fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C SHACL Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 010 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Words to Structure can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 010, From Words to Structure: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THE IDEA SOUNDS CLEAR. Until two people mean different things by the same noun.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/source-excerpts/build-010-source-excerpt-hold.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 1 alt text must identify Build 010, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2017 W3C®. W3C Document License linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2015/doc-license" }, { "slide": 2, "stage": "Problem", "copy": [ "THE IDEA SOUNDS CLEAR. Until two people mean different things by the same noun.", "The problem: From Words to Structure fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C SHACL Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 010 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Words to Structure can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 010, From Words to Structure: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: From Words to Structure fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THE IDEA SOUNDS CLEAR. Until two people mean different things by the same noun.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 010, 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." }, { "slide": 3, "stage": "System", "copy": [ "THE IDEA SOUNDS CLEAR. Until two people mean different things by the same noun.", "The problem: From Words to Structure fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C SHACL Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 010 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Words to Structure can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 010, From Words to Structure: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the From Words to Structure mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 010, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THE IDEA SOUNDS CLEAR. Until two people mean different things by the same noun.", "The problem: From Words to Structure fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C SHACL Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 010 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Words to Structure can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 010, From Words to Structure: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: W3C SHACL Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.w3.org/TR/2017/REC-shacl-20170720/; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 010, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2017 W3C®. Excerpt under the W3C Document License linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2015/doc-license Copyright © 2017 W3C®. W3C Document License linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2015/doc-license" }, { "slide": 5, "stage": "Demo", "copy": [ "THE IDEA SOUNDS CLEAR. Until two people mean different things by the same noun.", "The problem: From Words to Structure fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C SHACL Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 010 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Words to Structure can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 010, From Words to Structure: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 010 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 010, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 010, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THE IDEA SOUNDS CLEAR. Until two people mean different things by the same noun.", "The problem: From Words to Structure fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C SHACL Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 010 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Words to Structure can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 010, From Words to Structure: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: From Words to Structure can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 010, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THE IDEA SOUNDS CLEAR. Until two people mean different things by the same noun.", "The problem: From Words to Structure fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C SHACL Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 010 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Words to Structure can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 010, From Words to Structure: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 010, From Words to Structure: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 010, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 010, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "011", "title": "Same Name Is Not Same Entity", "template": "RN Builds 4:5 / evidence-and-governance / Build 011", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/011/build-011-linkedin-poster.png", "altText": "Build 011, Same Name Is Not Same Entity. Creator-owned 4:5 typographic opening frame. Visible text: “THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "W3C PROV Primer", "type": "official web standard", "relevance": "W3C PROV Primer is directly relevant to Same Name Is Not Same Entity and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that World Wide Web Consortium endorses RN or Build 011." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.", "The problem: Same Name Is Not Same Entity fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 011 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Name Is Not Same Entity can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 011, Same Name Is Not Same Entity: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/011/build-011-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 011, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.", "The problem: Same Name Is Not Same Entity fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 011 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Name Is Not Same Entity can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 011, Same Name Is Not Same Entity: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Same Name Is Not Same Entity fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 011, 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." }, { "slide": 3, "stage": "System", "copy": [ "THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.", "The problem: Same Name Is Not Same Entity fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 011 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Name Is Not Same Entity can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 011, Same Name Is Not Same Entity: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Same Name Is Not Same Entity mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 011, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.", "The problem: Same Name Is Not Same Entity fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 011 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Name Is Not Same Entity can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 011, Same Name Is Not Same Entity: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "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.", "claimBoundary": "Supports recognition of W3C PROV Primer and the limited source context adjacent to Build 011; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 011, 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." }, { "slide": 5, "stage": "Demo", "copy": [ "THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.", "The problem: Same Name Is Not Same Entity fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 011 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Name Is Not Same Entity can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 011, Same Name Is Not Same Entity: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 011 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 011, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 011, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.", "The problem: Same Name Is Not Same Entity fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 011 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Name Is Not Same Entity can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 011, Same Name Is Not Same Entity: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Same Name Is Not Same Entity can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 011, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THE RECORDS LOOK THE SAME. Similarity is a clue—not identity.", "The problem: Same Name Is Not Same Entity fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 011 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Name Is Not Same Entity can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 011, Same Name Is Not Same Entity: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 011, Same Name Is Not Same Entity: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 011, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 011, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "012", "title": "Controls Follow Consequence", "template": "RN Builds 4:5 / evidence-and-governance / Build 012", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-context/build-012-official-source-context.svg", "altText": "Official NIST AI 100-1 title-page text, selected as contextual evidence for Build 012, Controls Follow Consequence. Production source-context derivative; not evidence of prototype performance or institutional endorsement.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/012/build-012-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Controls Follow Consequence and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 012." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THE MODEL IS NOT THE USE. The same capability can carry radically different consequences in different contexts.", "The problem: Controls Follow Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 012 prototype. Show the interaction or decision path, not an invented result.", "Implication: Controls Follow Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 012, Controls Follow Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THE MODEL IS NOT THE USE. The same capability can carry radically different consequences in different contexts.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-context/build-012-official-source-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 012, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST public information · no endorsement" }, { "slide": 2, "stage": "Problem", "copy": [ "THE MODEL IS NOT THE USE. The same capability can carry radically different consequences in different contexts.", "The problem: Controls Follow Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 012 prototype. Show the interaction or decision path, not an invented result.", "Implication: Controls Follow Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 012, Controls Follow Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Controls Follow Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THE MODEL IS NOT THE USE. The same capability can carry radically different consequences in different contexts.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 012, 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." }, { "slide": 3, "stage": "System", "copy": [ "THE MODEL IS NOT THE USE. The same capability can carry radically different consequences in different contexts.", "The problem: Controls Follow Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 012 prototype. Show the interaction or decision path, not an invented result.", "Implication: Controls Follow Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 012, Controls Follow Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Controls Follow Consequence mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 012, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THE MODEL IS NOT THE USE. The same capability can carry radically different consequences in different contexts.", "The problem: Controls Follow Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 012 prototype. Show the interaction or decision path, not an invented result.", "Implication: Controls Follow Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 012, Controls Follow Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 012, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1. Republished courtesy of NIST. NIST public information · no endorsement" }, { "slide": 5, "stage": "Demo", "copy": [ "THE MODEL IS NOT THE USE. The same capability can carry radically different consequences in different contexts.", "The problem: Controls Follow Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 012 prototype. Show the interaction or decision path, not an invented result.", "Implication: Controls Follow Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 012, Controls Follow Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 012 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 012, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 012, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THE MODEL IS NOT THE USE. The same capability can carry radically different consequences in different contexts.", "The problem: Controls Follow Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 012 prototype. Show the interaction or decision path, not an invented result.", "Implication: Controls Follow Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 012, Controls Follow Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Controls Follow Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 012, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THE MODEL IS NOT THE USE. The same capability can carry radically different consequences in different contexts.", "The problem: Controls Follow Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 012 prototype. Show the interaction or decision path, not an invented result.", "Implication: Controls Follow Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 012, Controls Follow Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 012, Controls Follow Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 012, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 012, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "013", "title": "Follow the Consequence", "template": "RN Builds 4:5 / evidence-and-governance / Build 013", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/replacement-production-covers/build-013-official-excerpt-cover.svg", "altText": "Official NIST AI RMF MAP excerpt explaining how interdependent lifecycle activities and early decisions can alter later behavior, capabilities and impacts.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 24. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/013/build-013-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Follow the Consequence and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 013." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THE MODEL IS ONE STAGE. Consequence is produced by the full workflow around it.", "The problem: Follow the Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF: interdependent lifecycle activities can carry early decisions into later system impacts.", "Demo: walk through one bounded state change in the Build 013 prototype. Show the interaction or decision path, not an invented result.", "Implication: Follow the Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 013, Follow the Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THE MODEL IS ONE STAGE. Consequence is produced by the full workflow around it.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/replacement-production-covers/build-013-official-excerpt-cover.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports the general possibility of consequence propagation across an AI lifecycle; it does not establish the causal model or performance of Build 013.", "accessibility": "Slide 1 alt text must identify Build 013, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 2, "stage": "Problem", "copy": [ "THE MODEL IS ONE STAGE. Consequence is produced by the full workflow around it.", "The problem: Follow the Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF: interdependent lifecycle activities can carry early decisions into later system impacts.", "Demo: walk through one bounded state change in the Build 013 prototype. Show the interaction or decision path, not an invented result.", "Implication: Follow the Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 013, Follow the Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Follow the Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THE MODEL IS ONE STAGE. Consequence is produced by the full workflow around it.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 013, 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." }, { "slide": 3, "stage": "System", "copy": [ "THE MODEL IS ONE STAGE. Consequence is produced by the full workflow around it.", "The problem: Follow the Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF: interdependent lifecycle activities can carry early decisions into later system impacts.", "Demo: walk through one bounded state change in the Build 013 prototype. Show the interaction or decision path, not an invented result.", "Implication: Follow the Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 013, Follow the Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Follow the Consequence mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 013, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THE MODEL IS ONE STAGE. Consequence is produced by the full workflow around it.", "The problem: Follow the Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF: interdependent lifecycle activities can carry early decisions into later system impacts.", "Demo: walk through one bounded state change in the Build 013 prototype. Show the interaction or decision path, not an invented result.", "Implication: Follow the Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 013, Follow the Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: NIST AI RMF: interdependent lifecycle activities can carry early decisions into later system impacts.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports the general possibility of consequence propagation across an AI lifecycle; it does not establish the causal model or performance of Build 013.", "accessibility": "Slide 4 alt text must identify Build 013, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 24. Republished courtesy of NIST. NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 5, "stage": "Demo", "copy": [ "THE MODEL IS ONE STAGE. Consequence is produced by the full workflow around it.", "The problem: Follow the Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF: interdependent lifecycle activities can carry early decisions into later system impacts.", "Demo: walk through one bounded state change in the Build 013 prototype. Show the interaction or decision path, not an invented result.", "Implication: Follow the Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 013, Follow the Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 013 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 013, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 013, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THE MODEL IS ONE STAGE. Consequence is produced by the full workflow around it.", "The problem: Follow the Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF: interdependent lifecycle activities can carry early decisions into later system impacts.", "Demo: walk through one bounded state change in the Build 013 prototype. Show the interaction or decision path, not an invented result.", "Implication: Follow the Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 013, Follow the Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Follow the Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 013, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THE MODEL IS ONE STAGE. Consequence is produced by the full workflow around it.", "The problem: Follow the Consequence fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF: interdependent lifecycle activities can carry early decisions into later system impacts.", "Demo: walk through one bounded state change in the Build 013 prototype. Show the interaction or decision path, not an invented result.", "Implication: Follow the Consequence can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 013, Follow the Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 013, Follow the Consequence: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 013, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 013, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "014", "title": "The Answer Has Layers", "template": "RN Builds 4:5 / evidence-and-governance / Build 014", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/014/build-014-linkedin-poster.png", "altText": "Build 014, The Answer Has Layers. Creator-owned 4:5 typographic opening frame. Visible text: “THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "ABA Model Rules of Professional Conduct", "type": "official framework/document contextual anchor", "relevance": "ABA Model Rules of Professional Conduct is a directly relevant contextual authority or primary-source anchor for The Answer Has Layers; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: ABA Model Rules of Professional Conduct is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.", "The problem: The Answer Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 014 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Answer Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 014, The Answer Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/014/build-014-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 014, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.", "The problem: The Answer Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 014 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Answer Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 014, The Answer Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The Answer Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 014, 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." }, { "slide": 3, "stage": "System", "copy": [ "THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.", "The problem: The Answer Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 014 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Answer Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 014, The Answer Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Answer Has Layers mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 014, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.", "The problem: The Answer Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 014 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Answer Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 014, The Answer Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “ABA Model Rules of Professional Conduct” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Would contextualize professional-conduct source material relevant to Build 014; would not prove RN's legal system, advice quality, compliance or endorsement.", "accessibility": "Slide 4 alt text must identify Build 014, 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.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.", "The problem: The Answer Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 014 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Answer Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 014, The Answer Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 014 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 014, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 014, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.", "The problem: The Answer Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 014 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Answer Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 014, The Answer Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The Answer Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 014, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THE TOOL PRODUCED AN ANSWER. That does not tell you who researched, interpreted, inferred, decided, or approved.", "The problem: The Answer Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 014 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Answer Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 014, The Answer Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 014, The Answer Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 014, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 014, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "015", "title": "From Matter Work to Reusable System", "template": "RN Builds 4:5 / operations-and-provenance / Build 015", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/015/build-015-linkedin-poster.png", "altText": "Build 015, From Matter Work to Reusable System. Creator-owned 4:5 typographic opening frame. Visible text: “REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "ABA Model Rules of Professional Conduct", "type": "official framework/document contextual anchor", "relevance": "ABA Model Rules of Professional Conduct is a directly relevant contextual authority or primary-source anchor for From Matter Work to Reusable System; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: ABA Model Rules of Professional Conduct is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.", "The problem: From Matter Work to Reusable System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 015 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Matter Work to Reusable System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 015, From Matter Work to Reusable System: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/015/build-015-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 015, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.", "The problem: From Matter Work to Reusable System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 015 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Matter Work to Reusable System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 015, From Matter Work to Reusable System: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: From Matter Work to Reusable System fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 015, 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." }, { "slide": 3, "stage": "System", "copy": [ "REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.", "The problem: From Matter Work to Reusable System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 015 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Matter Work to Reusable System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 015, From Matter Work to Reusable System: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the From Matter Work to Reusable System mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 015, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.", "The problem: From Matter Work to Reusable System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 015 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Matter Work to Reusable System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 015, From Matter Work to Reusable System: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “ABA Model Rules of Professional Conduct” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Would contextualize professional-conduct source material relevant to Build 015; would not prove RN's legal system, advice quality, compliance or endorsement.", "accessibility": "Slide 4 alt text must identify Build 015, 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.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.", "The problem: From Matter Work to Reusable System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 015 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Matter Work to Reusable System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 015, From Matter Work to Reusable System: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 015 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 015, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 015, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.", "The problem: From Matter Work to Reusable System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 015 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Matter Work to Reusable System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 015, From Matter Work to Reusable System: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: From Matter Work to Reusable System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 015, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "REPEATED LEGAL TASK → PRODUCT ENGINE — Find which recurring supervised legal tasks can safely become reusable products or systems.", "The problem: From Matter Work to Reusable System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 015 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Matter Work to Reusable System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 015, From Matter Work to Reusable System: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 015, From Matter Work to Reusable System: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 015, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 015, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "016", "title": "The Matter Beneath the Matter", "template": "RN Builds 4:5 / operations-and-provenance / Build 016", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/016/build-016-linkedin-poster.png", "altText": "Build 016, The Matter Beneath the Matter. Creator-owned 4:5 typographic opening frame. Visible text: “LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "ABA Model Rules of Professional Conduct", "type": "official framework/document contextual anchor", "relevance": "ABA Model Rules of Professional Conduct is a directly relevant contextual authority or primary-source anchor for The Matter Beneath the Matter; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: ABA Model Rules of Professional Conduct is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.", "The problem: The Matter Beneath the Matter fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 016 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Matter Beneath the Matter can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 016, The Matter Beneath the Matter: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/016/build-016-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 016, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.", "The problem: The Matter Beneath the Matter fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 016 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Matter Beneath the Matter can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 016, The Matter Beneath the Matter: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The Matter Beneath the Matter fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 016, 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." }, { "slide": 3, "stage": "System", "copy": [ "LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.", "The problem: The Matter Beneath the Matter fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 016 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Matter Beneath the Matter can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 016, The Matter Beneath the Matter: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Matter Beneath the Matter mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 016, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.", "The problem: The Matter Beneath the Matter fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 016 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Matter Beneath the Matter can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 016, The Matter Beneath the Matter: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “ABA Model Rules of Professional Conduct” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Would contextualize professional-conduct source material relevant to Build 016; would not prove RN's legal system, advice quality, compliance or endorsement.", "accessibility": "Slide 4 alt text must identify Build 016, 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.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.", "The problem: The Matter Beneath the Matter fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 016 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Matter Beneath the Matter can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 016, The Matter Beneath the Matter: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 016 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 016, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 016, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.", "The problem: The Matter Beneath the Matter fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 016 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Matter Beneath the Matter can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 016, The Matter Beneath the Matter: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The Matter Beneath the Matter can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 016, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "LEGAL WORKFLOW MAPPING — Map actors, documents, authorities, handoffs, deadlines, decisions, risks and records across legal work.", "The problem: The Matter Beneath the Matter fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: ABA Model Rules of Professional Conduct frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 016 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Matter Beneath the Matter can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 016, The Matter Beneath the Matter: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 016, The Matter Beneath the Matter: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 016, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 016, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "017", "title": "The Risk Lives Between the Boxes", "template": "RN Builds 4:5 / operations-and-provenance / Build 017", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/replacement-production-covers/build-017-official-excerpt-cover.svg", "altText": "Official NIST AI RMF GOVERN 2 excerpt requiring clear roles and communication lines, trained personnel and partners, and executive responsibility for AI-risk decisions.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 23. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/017/build-017-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to The Risk Lives Between the Boxes and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 017." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "REGULATED-MARKET HANDOFF MAPPER — Find where responsibility, evidence, consent and accountability disappear between organizations.", "The problem: The Risk Lives Between the Boxes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 2 assigns clear communication lines, partner duties and executive responsibility across organizational handoffs.", "Demo: walk through one bounded state change in the Build 017 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Risk Lives Between the Boxes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 017, The Risk Lives Between the Boxes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "REGULATED-MARKET HANDOFF MAPPER — Find where responsibility, evidence, consent and accountability disappear between organizations.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/replacement-production-covers/build-017-official-excerpt-cover.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports documenting responsibility and communication across teams and partners; it does not prove Build 017 resolves organizational handoff risk.", "accessibility": "Slide 1 alt text must identify Build 017, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 2, "stage": "Problem", "copy": [ "REGULATED-MARKET HANDOFF MAPPER — Find where responsibility, evidence, consent and accountability disappear between organizations.", "The problem: The Risk Lives Between the Boxes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 2 assigns clear communication lines, partner duties and executive responsibility across organizational handoffs.", "Demo: walk through one bounded state change in the Build 017 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Risk Lives Between the Boxes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 017, The Risk Lives Between the Boxes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The Risk Lives Between the Boxes fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “REGULATED-MARKET HANDOFF MAPPER — Find where responsibility, evidence, consent and accountability disappear between organizations.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 017, 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." }, { "slide": 3, "stage": "System", "copy": [ "REGULATED-MARKET HANDOFF MAPPER — Find where responsibility, evidence, consent and accountability disappear between organizations.", "The problem: The Risk Lives Between the Boxes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 2 assigns clear communication lines, partner duties and executive responsibility across organizational handoffs.", "Demo: walk through one bounded state change in the Build 017 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Risk Lives Between the Boxes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 017, The Risk Lives Between the Boxes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Risk Lives Between the Boxes mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 017, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "REGULATED-MARKET HANDOFF MAPPER — Find where responsibility, evidence, consent and accountability disappear between organizations.", "The problem: The Risk Lives Between the Boxes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 2 assigns clear communication lines, partner duties and executive responsibility across organizational handoffs.", "Demo: walk through one bounded state change in the Build 017 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Risk Lives Between the Boxes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 017, The Risk Lives Between the Boxes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: NIST AI RMF GOVERN 2 assigns clear communication lines, partner duties and executive responsibility across organizational handoffs.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports documenting responsibility and communication across teams and partners; it does not prove Build 017 resolves organizational handoff risk.", "accessibility": "Slide 4 alt text must identify Build 017, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 23. Republished courtesy of NIST. NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 5, "stage": "Demo", "copy": [ "REGULATED-MARKET HANDOFF MAPPER — Find where responsibility, evidence, consent and accountability disappear between organizations.", "The problem: The Risk Lives Between the Boxes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 2 assigns clear communication lines, partner duties and executive responsibility across organizational handoffs.", "Demo: walk through one bounded state change in the Build 017 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Risk Lives Between the Boxes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 017, The Risk Lives Between the Boxes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 017 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 017, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 017, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "REGULATED-MARKET HANDOFF MAPPER — Find where responsibility, evidence, consent and accountability disappear between organizations.", "The problem: The Risk Lives Between the Boxes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 2 assigns clear communication lines, partner duties and executive responsibility across organizational handoffs.", "Demo: walk through one bounded state change in the Build 017 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Risk Lives Between the Boxes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 017, The Risk Lives Between the Boxes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The Risk Lives Between the Boxes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 017, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "REGULATED-MARKET HANDOFF MAPPER — Find where responsibility, evidence, consent and accountability disappear between organizations.", "The problem: The Risk Lives Between the Boxes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF GOVERN 2 assigns clear communication lines, partner duties and executive responsibility across organizational handoffs.", "Demo: walk through one bounded state change in the Build 017 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Risk Lives Between the Boxes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 017, The Risk Lives Between the Boxes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 017, The Risk Lives Between the Boxes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 017, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 017, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "018", "title": "The Process Is Part of the Outcome", "template": "RN Builds 4:5 / operations-and-provenance / Build 018", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-variants/build-018-official-context.svg", "altText": "Build 018, The Process Is Part of the Outcome. Official GOV.UK Service Standard document or guidance page, selected as contextual evidence for Build 018, The Process Is Part of the Outcome.", "credit": "Contains public sector information licensed under the Open Government Licence v3.0. Source: UK Government Digital Service, GOV.UK Service Standard.", "sourceUrl": "https://www.gov.uk/service-manual/service-standard", "rollbackAssetUrl": "/media/builds/018/build-018-linkedin-poster.png" }, "recognizableEntity": { "label": "GOV.UK Service Standard", "type": "official government guidance", "relevance": "GOV.UK Service Standard is directly relevant to The Process Is Part of the Outcome and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that UK Government Digital Service endorses RN or Build 018." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "INSTITUTIONAL FRICTION DETECTOR — Find bottlenecks, dead ends, repeated loops and avoidable burden inside institutional processes.", "The problem: The Process Is Part of the Outcome fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 018 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Process Is Part of the Outcome can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 018, The Process Is Part of the Outcome: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "INSTITUTIONAL FRICTION DETECTOR — Find bottlenecks, dead ends, repeated loops and avoidable burden inside institutional processes.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-variants/build-018-official-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of GOV.UK Service Standard and the limited source context adjacent to Build 018; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 018, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Open Government Licence v3.0 · Crown copyright source" }, { "slide": 2, "stage": "Problem", "copy": [ "INSTITUTIONAL FRICTION DETECTOR — Find bottlenecks, dead ends, repeated loops and avoidable burden inside institutional processes.", "The problem: The Process Is Part of the Outcome fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 018 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Process Is Part of the Outcome can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 018, The Process Is Part of the Outcome: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The Process Is Part of the Outcome fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “INSTITUTIONAL FRICTION DETECTOR — Find bottlenecks, dead ends, repeated loops and avoidable burden inside institutional processes.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 018, 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." }, { "slide": 3, "stage": "System", "copy": [ "INSTITUTIONAL FRICTION DETECTOR — Find bottlenecks, dead ends, repeated loops and avoidable burden inside institutional processes.", "The problem: The Process Is Part of the Outcome fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 018 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Process Is Part of the Outcome can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 018, The Process Is Part of the Outcome: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Process Is Part of the Outcome mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 018, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "INSTITUTIONAL FRICTION DETECTOR — Find bottlenecks, dead ends, repeated loops and avoidable burden inside institutional processes.", "The problem: The Process Is Part of the Outcome fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 018 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Process Is Part of the Outcome can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 018, The Process Is Part of the Outcome: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.gov.uk/service-manual/service-standard; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of GOV.UK Service Standard and the limited source context adjacent to Build 018; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 018, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Contains public sector information licensed under the Open Government Licence v3.0. Source: UK Government Digital Service, GOV.UK Service Standard. Open Government Licence v3.0 · Crown copyright source" }, { "slide": 5, "stage": "Demo", "copy": [ "INSTITUTIONAL FRICTION DETECTOR — Find bottlenecks, dead ends, repeated loops and avoidable burden inside institutional processes.", "The problem: The Process Is Part of the Outcome fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 018 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Process Is Part of the Outcome can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 018, The Process Is Part of the Outcome: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 018 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 018, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 018, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "INSTITUTIONAL FRICTION DETECTOR — Find bottlenecks, dead ends, repeated loops and avoidable burden inside institutional processes.", "The problem: The Process Is Part of the Outcome fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 018 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Process Is Part of the Outcome can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 018, The Process Is Part of the Outcome: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The Process Is Part of the Outcome can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 018, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "INSTITUTIONAL FRICTION DETECTOR — Find bottlenecks, dead ends, repeated loops and avoidable burden inside institutional processes.", "The problem: The Process Is Part of the Outcome fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The GOV.UK Service Standard, shown as public-service design context.", "Demo: walk through one bounded state change in the Build 018 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Process Is Part of the Outcome can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 018, The Process Is Part of the Outcome: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 018, The Process Is Part of the Outcome: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 018, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 018, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "019", "title": "The Alert That Knows Who Cares", "template": "RN Builds 4:5 / operations-and-provenance / Build 019", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-context/build-019-official-source-context.svg", "altText": "Official NIST SP 800-61r3 title-page text, selected as contextual evidence for Build 019, The Alert That Knows Who Cares. Production source-context derivative; not evidence of prototype performance or institutional endorsement.", "credit": "Nelson, A. et al. (2025), Incident Response Recommendations and Considerations for Cybersecurity Risk Management, NIST SP 800-61 Rev. 3. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.SP.800-61r3", "rollbackAssetUrl": "/media/builds/019/build-019-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST SP 800-61 Rev. 3", "type": "official technical publication", "relevance": "NIST SP 800-61 Rev. 3 is directly relevant to The Alert That Knows Who Cares and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 019." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "100 ALERTS ≠ 100 INCIDENTS. Repeated signals can describe one consequential event—not one hundred separate interruptions.", "The problem: The Alert That Knows Who Cares fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST SP 800-61 Rev. 3, shown as incident-response context.", "Demo: walk through one bounded state change in the Build 019 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Alert That Knows Who Cares can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 019, The Alert That Knows Who Cares: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "100 ALERTS ≠ 100 INCIDENTS. Repeated signals can describe one consequential event—not one hundred separate interruptions.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-context/build-019-official-source-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 019, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST public information · no endorsement" }, { "slide": 2, "stage": "Problem", "copy": [ "100 ALERTS ≠ 100 INCIDENTS. Repeated signals can describe one consequential event—not one hundred separate interruptions.", "The problem: The Alert That Knows Who Cares fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST SP 800-61 Rev. 3, shown as incident-response context.", "Demo: walk through one bounded state change in the Build 019 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Alert That Knows Who Cares can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 019, The Alert That Knows Who Cares: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The Alert That Knows Who Cares fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “100 ALERTS ≠ 100 INCIDENTS. Repeated signals can describe one consequential event—not one hundred separate interruptions.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 019, 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." }, { "slide": 3, "stage": "System", "copy": [ "100 ALERTS ≠ 100 INCIDENTS. Repeated signals can describe one consequential event—not one hundred separate interruptions.", "The problem: The Alert That Knows Who Cares fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST SP 800-61 Rev. 3, shown as incident-response context.", "Demo: walk through one bounded state change in the Build 019 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Alert That Knows Who Cares can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 019, The Alert That Knows Who Cares: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Alert That Knows Who Cares mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 019, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "100 ALERTS ≠ 100 INCIDENTS. Repeated signals can describe one consequential event—not one hundred separate interruptions.", "The problem: The Alert That Knows Who Cares fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST SP 800-61 Rev. 3, shown as incident-response context.", "Demo: walk through one bounded state change in the Build 019 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Alert That Knows Who Cares can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 019, The Alert That Knows Who Cares: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: Official NIST SP 800-61 Rev. 3, shown as incident-response context.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.SP.800-61r3; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 019, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Nelson, A. et al. (2025), Incident Response Recommendations and Considerations for Cybersecurity Risk Management, NIST SP 800-61 Rev. 3. Republished courtesy of NIST. NIST public information · no endorsement" }, { "slide": 5, "stage": "Demo", "copy": [ "100 ALERTS ≠ 100 INCIDENTS. Repeated signals can describe one consequential event—not one hundred separate interruptions.", "The problem: The Alert That Knows Who Cares fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST SP 800-61 Rev. 3, shown as incident-response context.", "Demo: walk through one bounded state change in the Build 019 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Alert That Knows Who Cares can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 019, The Alert That Knows Who Cares: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 019 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 019, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 019, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "100 ALERTS ≠ 100 INCIDENTS. Repeated signals can describe one consequential event—not one hundred separate interruptions.", "The problem: The Alert That Knows Who Cares fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST SP 800-61 Rev. 3, shown as incident-response context.", "Demo: walk through one bounded state change in the Build 019 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Alert That Knows Who Cares can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 019, The Alert That Knows Who Cares: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The Alert That Knows Who Cares can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 019, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "100 ALERTS ≠ 100 INCIDENTS. Repeated signals can describe one consequential event—not one hundred separate interruptions.", "The problem: The Alert That Knows Who Cares fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST SP 800-61 Rev. 3, shown as incident-response context.", "Demo: walk through one bounded state change in the Build 019 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Alert That Knows Who Cares can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 019, The Alert That Knows Who Cares: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 019, The Alert That Knows Who Cares: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 019, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 019, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "020", "title": "Open the Decision", "template": "RN Builds 4:5 / operations-and-provenance / Build 020", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/020/build-020-linkedin-poster.png", "altText": "Build 020, Open the Decision. Creator-owned 4:5 typographic opening frame. Visible text: “A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "W3C PROV Primer", "type": "official web standard", "relevance": "W3C PROV Primer is directly relevant to Open the Decision and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that World Wide Web Consortium endorses RN or Build 020." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.", "The problem: Open the Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 020 prototype. Show the interaction or decision path, not an invented result.", "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.", "Explore Build 020, Open the Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.", "visualGuidance": "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.", "claimBoundary": "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." }, { "slide": 2, "stage": "Problem", "copy": [ "A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.", "The problem: Open the Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 020 prototype. Show the interaction or decision path, not an invented result.", "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.", "Explore Build 020, Open the Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Open the Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "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.", "claimBoundary": "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." }, { "slide": 3, "stage": "System", "copy": [ "A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.", "The problem: Open the Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 020 prototype. Show the interaction or decision path, not an invented result.", "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.", "Explore Build 020, Open the Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "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.", "claimBoundary": "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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.", "The problem: Open the Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 020 prototype. Show the interaction or decision path, not an invented result.", "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.", "Explore Build 020, Open the Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "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.", "claimBoundary": "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." }, { "slide": 5, "stage": "Demo", "copy": [ "A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.", "The problem: Open the Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 020 prototype. Show the interaction or decision path, not an invented result.", "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.", "Explore Build 020, Open the Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 020 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "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.", "claimBoundary": "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." }, { "slide": 6, "stage": "Implications", "copy": [ "A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.", "The problem: Open the Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 020 prototype. Show the interaction or decision path, not an invented result.", "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.", "Explore Build 020, Open the Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "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.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A DECISION IS NOT A SNAPSHOT. Accountability requires the actor, authority, time, evidence, alternatives, acknowledgement, result, and corrections.", "The problem: Open the Decision fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C PROV Primer frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 020 prototype. Show the interaction or decision path, not an invented result.", "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.", "Explore Build 020, Open the Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 020, Open the Decision: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "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.", "claimBoundary": "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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "021", "title": "Break the Promise Open", "template": "RN Builds 4:5 / operations-and-provenance / Build 021", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/021/build-021-linkedin-poster.png", "altText": "Build 021, Break the Promise Open. Creator-owned 4:5 typographic opening frame. Visible text: “THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Break the Promise Open and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 021." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.", "The problem: Break the Promise Open fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 021 prototype. Show the interaction or decision path, not an invented result.", "Implication: Break the Promise Open can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 021, Break the Promise Open: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/021/build-021-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 021, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.", "The problem: Break the Promise Open fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 021 prototype. Show the interaction or decision path, not an invented result.", "Implication: Break the Promise Open can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 021, Break the Promise Open: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Break the Promise Open fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 021, 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." }, { "slide": 3, "stage": "System", "copy": [ "THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.", "The problem: Break the Promise Open fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 021 prototype. Show the interaction or decision path, not an invented result.", "Implication: Break the Promise Open can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 021, Break the Promise Open: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Break the Promise Open mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 021, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.", "The problem: Break the Promise Open fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 021 prototype. Show the interaction or decision path, not an invented result.", "Implication: Break the Promise Open can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 021, Break the Promise Open: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST AI Risk Management Framework 1.0” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Supports recognition of NIST AI Risk Management Framework 1.0 and the limited source context adjacent to Build 021; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 021, 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://doi.org/10.6028/NIST.AI.100-1; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.", "The problem: Break the Promise Open fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 021 prototype. Show the interaction or decision path, not an invented result.", "Implication: Break the Promise Open can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 021, Break the Promise Open: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 021 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 021, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 021, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.", "The problem: Break the Promise Open fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 021 prototype. Show the interaction or decision path, not an invented result.", "Implication: Break the Promise Open can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 021, Break the Promise Open: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Break the Promise Open can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 021, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THE CLAIM SOUNDS CERTAIN. Procurement still needs to know what the evidence can actually support.", "The problem: Break the Promise Open fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 021 prototype. Show the interaction or decision path, not an invented result.", "Implication: Break the Promise Open can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 021, Break the Promise Open: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 021, Break the Promise Open: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 021, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 021, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "022", "title": "Human Impact Nodes", "template": "RN Builds 4:5 / operations-and-provenance / Build 022", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-context/build-022-official-source-context.svg", "altText": "Official NIST AI 100-1 title-page text, selected as contextual evidence for Build 022, Human Impact Nodes. Production source-context derivative; not evidence of prototype performance or institutional endorsement.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/022/build-022-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Human Impact Nodes and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 022." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "HUMAN CONSEQUENCE MAP FOR AI WORKFLOWS — Show who can be affected by an AI workflow and how consequences travel to them.", "The problem: Human Impact Nodes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 022 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Impact Nodes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 022, Human Impact Nodes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "HUMAN CONSEQUENCE MAP FOR AI WORKFLOWS — Show who can be affected by an AI workflow and how consequences travel to them.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-context/build-022-official-source-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 022, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST public information · no endorsement" }, { "slide": 2, "stage": "Problem", "copy": [ "HUMAN CONSEQUENCE MAP FOR AI WORKFLOWS — Show who can be affected by an AI workflow and how consequences travel to them.", "The problem: Human Impact Nodes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 022 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Impact Nodes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 022, Human Impact Nodes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Human Impact Nodes fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “HUMAN CONSEQUENCE MAP FOR AI WORKFLOWS — Show who can be affected by an AI workflow and how consequences travel to them.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 022, 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." }, { "slide": 3, "stage": "System", "copy": [ "HUMAN CONSEQUENCE MAP FOR AI WORKFLOWS — Show who can be affected by an AI workflow and how consequences travel to them.", "The problem: Human Impact Nodes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 022 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Impact Nodes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 022, Human Impact Nodes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Human Impact Nodes mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 022, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "HUMAN CONSEQUENCE MAP FOR AI WORKFLOWS — Show who can be affected by an AI workflow and how consequences travel to them.", "The problem: Human Impact Nodes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 022 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Impact Nodes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 022, Human Impact Nodes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 022, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1. Republished courtesy of NIST. NIST public information · no endorsement" }, { "slide": 5, "stage": "Demo", "copy": [ "HUMAN CONSEQUENCE MAP FOR AI WORKFLOWS — Show who can be affected by an AI workflow and how consequences travel to them.", "The problem: Human Impact Nodes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 022 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Impact Nodes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 022, Human Impact Nodes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 022 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 022, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 022, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "HUMAN CONSEQUENCE MAP FOR AI WORKFLOWS — Show who can be affected by an AI workflow and how consequences travel to them.", "The problem: Human Impact Nodes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 022 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Impact Nodes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 022, Human Impact Nodes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Human Impact Nodes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 022, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "HUMAN CONSEQUENCE MAP FOR AI WORKFLOWS — Show who can be affected by an AI workflow and how consequences travel to them.", "The problem: Human Impact Nodes fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST AI Risk Management Framework 1.0, shown as bounded source context.", "Demo: walk through one bounded state change in the Build 022 prototype. Show the interaction or decision path, not an invented result.", "Implication: Human Impact Nodes can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 022, Human Impact Nodes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 022, Human Impact Nodes: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 022, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 022, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "023", "title": "Consent That Can Change Its Mind", "template": "RN Builds 4:5 / operations-and-provenance / Build 023", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/023/build-023-linkedin-poster.png", "altText": "Build 023, Consent That Can Change Its Mind. Creator-owned 4:5 typographic opening frame. Visible text: “BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Regulation (EU) 2016/679", "type": "official legal publication", "relevance": "Regulation (EU) 2016/679 is directly relevant to Consent That Can Change Its Mind and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that European Union / EUR-Lex endorses RN or Build 023." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.", "The problem: Consent That Can Change Its Mind fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 023 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consent That Can Change Its Mind can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 023, Consent That Can Change Its Mind: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/023/build-023-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 023, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.", "The problem: Consent That Can Change Its Mind fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 023 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consent That Can Change Its Mind can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 023, Consent That Can Change Its Mind: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Consent That Can Change Its Mind fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 023, 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." }, { "slide": 3, "stage": "System", "copy": [ "BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.", "The problem: Consent That Can Change Its Mind fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 023 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consent That Can Change Its Mind can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 023, Consent That Can Change Its Mind: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Consent That Can Change Its Mind mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 023, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.", "The problem: Consent That Can Change Its Mind fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 023 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consent That Can Change Its Mind can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 023, Consent That Can Change Its Mind: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Regulation (EU) 2016/679” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Supports recognition of Regulation (EU) 2016/679 and the limited source context adjacent to Build 023; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 023, 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://eur-lex.europa.eu/eli/reg/2016/679/oj; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.", "The problem: Consent That Can Change Its Mind fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 023 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consent That Can Change Its Mind can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 023, Consent That Can Change Its Mind: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 023 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 023, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 023, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.", "The problem: Consent That Can Change Its Mind fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 023 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consent That Can Change Its Mind can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 023, Consent That Can Change Its Mind: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Consent That Can Change Its Mind can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 023, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "BUNDLED CONSENT HIDES THE DEAL — A single yes cannot show purpose, data, recipient, retention, reuse, or withdrawal.", "The problem: Consent That Can Change Its Mind fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 023 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consent That Can Change Its Mind can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 023, Consent That Can Change Its Mind: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 023, Consent That Can Change Its Mind: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 023, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 023, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "024", "title": "The Best Data Risk Is Data Never Collected", "template": "RN Builds 4:5 / operations-and-provenance / Build 024", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/024/build-024-linkedin-poster.png", "altText": "Build 024, The Best Data Risk Is Data Never Collected. Creator-owned 4:5 typographic opening frame. Visible text: “MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Regulation (EU) 2016/679", "type": "official legal publication", "relevance": "Regulation (EU) 2016/679 is directly relevant to The Best Data Risk Is Data Never Collected and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that European Union / EUR-Lex endorses RN or Build 024." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.", "The problem: The Best Data Risk Is Data Never Collected fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 024 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Best Data Risk Is Data Never Collected can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 024, The Best Data Risk Is Data Never Collected: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/024/build-024-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 024, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.", "The problem: The Best Data Risk Is Data Never Collected fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 024 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Best Data Risk Is Data Never Collected can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 024, The Best Data Risk Is Data Never Collected: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The Best Data Risk Is Data Never Collected fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 024, 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." }, { "slide": 3, "stage": "System", "copy": [ "MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.", "The problem: The Best Data Risk Is Data Never Collected fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 024 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Best Data Risk Is Data Never Collected can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 024, The Best Data Risk Is Data Never Collected: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Best Data Risk Is Data Never Collected mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 024, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.", "The problem: The Best Data Risk Is Data Never Collected fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 024 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Best Data Risk Is Data Never Collected can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 024, The Best Data Risk Is Data Never Collected: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Regulation (EU) 2016/679” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Supports recognition of Regulation (EU) 2016/679 and the limited source context adjacent to Build 024; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 024, 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://eur-lex.europa.eu/eli/reg/2016/679/oj; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.", "The problem: The Best Data Risk Is Data Never Collected fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 024 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Best Data Risk Is Data Never Collected can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 024, The Best Data Risk Is Data Never Collected: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 024 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 024, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 024, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.", "The problem: The Best Data Risk Is Data Never Collected fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 024 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Best Data Risk Is Data Never Collected can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 024, The Best Data Risk Is Data Never Collected: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The Best Data Risk Is Data Never Collected can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 024, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "MORE DATA IS NOT MORE INTELLIGENCE — Every collected field creates exposure, retention work, access pathways, and eventual deletion duties.", "The problem: The Best Data Risk Is Data Never Collected fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulation (EU) 2016/679 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 024 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Best Data Risk Is Data Never Collected can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 024, The Best Data Risk Is Data Never Collected: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 024, The Best Data Risk Is Data Never Collected: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 024, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 024, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "025", "title": "Readiness Has Layers", "template": "RN Builds 4:5 / operations-and-provenance / Build 025", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/replacement-production-covers/build-025-official-excerpt-cover.svg", "altText": "Official NIST AI RMF Profiles excerpt explaining current state, target state, gaps, action plans, prioritization and resources.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 33. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/025/build-025-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Readiness Has Layers and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 025." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A USE CASE IS NOT AN IMPLEMENTATION PLAN — A promising capability can still outrun the organization expected to operate it.", "The problem: Readiness Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF Current and Target Profiles expose readiness gaps and the resources required to close them.", "Demo: walk through one bounded state change in the Build 025 prototype. Show the interaction or decision path, not an invented result.", "Implication: Readiness Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 025, Readiness Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A USE CASE IS NOT AN IMPLEMENTATION PLAN — A promising capability can still outrun the organization expected to operate it.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/replacement-production-covers/build-025-official-excerpt-cover.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports layered current-to-target readiness analysis; it does not certify an organization or validate Build 025’s scoring.", "accessibility": "Slide 1 alt text must identify Build 025, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 2, "stage": "Problem", "copy": [ "A USE CASE IS NOT AN IMPLEMENTATION PLAN — A promising capability can still outrun the organization expected to operate it.", "The problem: Readiness Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF Current and Target Profiles expose readiness gaps and the resources required to close them.", "Demo: walk through one bounded state change in the Build 025 prototype. Show the interaction or decision path, not an invented result.", "Implication: Readiness Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 025, Readiness Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Readiness Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A USE CASE IS NOT AN IMPLEMENTATION PLAN — A promising capability can still outrun the organization expected to operate it.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 025, 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." }, { "slide": 3, "stage": "System", "copy": [ "A USE CASE IS NOT AN IMPLEMENTATION PLAN — A promising capability can still outrun the organization expected to operate it.", "The problem: Readiness Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF Current and Target Profiles expose readiness gaps and the resources required to close them.", "Demo: walk through one bounded state change in the Build 025 prototype. Show the interaction or decision path, not an invented result.", "Implication: Readiness Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 025, Readiness Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Readiness Has Layers mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 025, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A USE CASE IS NOT AN IMPLEMENTATION PLAN — A promising capability can still outrun the organization expected to operate it.", "The problem: Readiness Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF Current and Target Profiles expose readiness gaps and the resources required to close them.", "Demo: walk through one bounded state change in the Build 025 prototype. Show the interaction or decision path, not an invented result.", "Implication: Readiness Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 025, Readiness Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: NIST AI RMF Current and Target Profiles expose readiness gaps and the resources required to close them.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports layered current-to-target readiness analysis; it does not certify an organization or validate Build 025’s scoring.", "accessibility": "Slide 4 alt text must identify Build 025, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 33. Republished courtesy of NIST. NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 5, "stage": "Demo", "copy": [ "A USE CASE IS NOT AN IMPLEMENTATION PLAN — A promising capability can still outrun the organization expected to operate it.", "The problem: Readiness Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF Current and Target Profiles expose readiness gaps and the resources required to close them.", "Demo: walk through one bounded state change in the Build 025 prototype. Show the interaction or decision path, not an invented result.", "Implication: Readiness Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 025, Readiness Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 025 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 025, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 025, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A USE CASE IS NOT AN IMPLEMENTATION PLAN — A promising capability can still outrun the organization expected to operate it.", "The problem: Readiness Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF Current and Target Profiles expose readiness gaps and the resources required to close them.", "Demo: walk through one bounded state change in the Build 025 prototype. Show the interaction or decision path, not an invented result.", "Implication: Readiness Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 025, Readiness Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Readiness Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 025, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A USE CASE IS NOT AN IMPLEMENTATION PLAN — A promising capability can still outrun the organization expected to operate it.", "The problem: Readiness Has Layers fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF Current and Target Profiles expose readiness gaps and the resources required to close them.", "Demo: walk through one bounded state change in the Build 025 prototype. Show the interaction or decision path, not an invented result.", "Implication: Readiness Has Layers can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 025, Readiness Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 025, Readiness Has Layers: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 025, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 025, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "026", "title": "Records Normalize Without Losing Their Past", "template": "RN Builds 4:5 / operations-and-provenance / Build 026", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-variants/build-026-official-context.svg", "altText": "Build 026, Records Normalize Without Losing Their Past. Official W3C PROV-O document or guidance page, selected as contextual evidence for Build 026, Records Normalize Without Losing Their Past.", "credit": "Copyright © 2013 W3C®. Material reproduced from PROV-O, https://www.w3.org/TR/prov-o/, under the W3C Document License.", "sourceUrl": "https://www.w3.org/TR/prov-o/", "rollbackAssetUrl": "/media/builds/026/build-026-linkedin-poster.png" }, "recognizableEntity": { "label": "W3C PROV-O", "type": "official web standard", "relevance": "W3C PROV-O is directly relevant to Records Normalize Without Losing Their Past and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that World Wide Web Consortium endorses RN or Build 026." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A CLEAN TABLE CAN HIDE A MESSY HISTORY — Completeness on screen does not prove the records are accurate, representative, current, or fit for this decision.", "The problem: Records Normalize Without Losing Their Past fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The W3C PROV-O Recommendation, shown as provenance-vocabulary context.", "Demo: walk through one bounded state change in the Build 026 prototype. Show the interaction or decision path, not an invented result.", "Implication: Records Normalize Without Losing Their Past can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 026, Records Normalize Without Losing Their Past: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A CLEAN TABLE CAN HIDE A MESSY HISTORY — Completeness on screen does not prove the records are accurate, representative, current, or fit for this decision.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-variants/build-026-official-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of W3C PROV-O and the limited source context adjacent to Build 026; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 026, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "W3C Document License · © 2013 W3C®" }, { "slide": 2, "stage": "Problem", "copy": [ "A CLEAN TABLE CAN HIDE A MESSY HISTORY — Completeness on screen does not prove the records are accurate, representative, current, or fit for this decision.", "The problem: Records Normalize Without Losing Their Past fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The W3C PROV-O Recommendation, shown as provenance-vocabulary context.", "Demo: walk through one bounded state change in the Build 026 prototype. Show the interaction or decision path, not an invented result.", "Implication: Records Normalize Without Losing Their Past can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 026, Records Normalize Without Losing Their Past: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Records Normalize Without Losing Their Past fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A CLEAN TABLE CAN HIDE A MESSY HISTORY — Completeness on screen does not prove the records are accurate, representative, current, or fit for this decision.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 026, 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." }, { "slide": 3, "stage": "System", "copy": [ "A CLEAN TABLE CAN HIDE A MESSY HISTORY — Completeness on screen does not prove the records are accurate, representative, current, or fit for this decision.", "The problem: Records Normalize Without Losing Their Past fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The W3C PROV-O Recommendation, shown as provenance-vocabulary context.", "Demo: walk through one bounded state change in the Build 026 prototype. Show the interaction or decision path, not an invented result.", "Implication: Records Normalize Without Losing Their Past can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 026, Records Normalize Without Losing Their Past: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Records Normalize Without Losing Their Past mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 026, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A CLEAN TABLE CAN HIDE A MESSY HISTORY — Completeness on screen does not prove the records are accurate, representative, current, or fit for this decision.", "The problem: Records Normalize Without Losing Their Past fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The W3C PROV-O Recommendation, shown as provenance-vocabulary context.", "Demo: walk through one bounded state change in the Build 026 prototype. Show the interaction or decision path, not an invented result.", "Implication: Records Normalize Without Losing Their Past can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 026, Records Normalize Without Losing Their Past: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: The W3C PROV-O Recommendation, shown as provenance-vocabulary context.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.w3.org/TR/prov-o/; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of W3C PROV-O and the limited source context adjacent to Build 026; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 026, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2013 W3C®. Material reproduced from PROV-O, https://www.w3.org/TR/prov-o/, under the W3C Document License. W3C Document License · © 2013 W3C®" }, { "slide": 5, "stage": "Demo", "copy": [ "A CLEAN TABLE CAN HIDE A MESSY HISTORY — Completeness on screen does not prove the records are accurate, representative, current, or fit for this decision.", "The problem: Records Normalize Without Losing Their Past fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The W3C PROV-O Recommendation, shown as provenance-vocabulary context.", "Demo: walk through one bounded state change in the Build 026 prototype. Show the interaction or decision path, not an invented result.", "Implication: Records Normalize Without Losing Their Past can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 026, Records Normalize Without Losing Their Past: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 026 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 026, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 026, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A CLEAN TABLE CAN HIDE A MESSY HISTORY — Completeness on screen does not prove the records are accurate, representative, current, or fit for this decision.", "The problem: Records Normalize Without Losing Their Past fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The W3C PROV-O Recommendation, shown as provenance-vocabulary context.", "Demo: walk through one bounded state change in the Build 026 prototype. Show the interaction or decision path, not an invented result.", "Implication: Records Normalize Without Losing Their Past can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 026, Records Normalize Without Losing Their Past: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Records Normalize Without Losing Their Past can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 026, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A CLEAN TABLE CAN HIDE A MESSY HISTORY — Completeness on screen does not prove the records are accurate, representative, current, or fit for this decision.", "The problem: Records Normalize Without Losing Their Past fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: The W3C PROV-O Recommendation, shown as provenance-vocabulary context.", "Demo: walk through one bounded state change in the Build 026 prototype. Show the interaction or decision path, not an invented result.", "Implication: Records Normalize Without Losing Their Past can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 026, Records Normalize Without Losing Their Past: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 026, Records Normalize Without Losing Their Past: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 026, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 026, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "027", "title": "Ownership Exposure Board", "template": "RN Builds 4:5 / operations-and-provenance / Build 027", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/027/build-027-linkedin-poster.png", "altText": "Build 027, Ownership Exposure Board. Creator-owned 4:5 typographic opening frame. Visible text: “POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Copyright Basics, Circular 1", "type": "official framework/document contextual anchor", "relevance": "Copyright Basics, Circular 1 is a directly relevant contextual authority or primary-source anchor for Ownership Exposure Board; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: Copyright Basics, Circular 1 is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.", "The problem: Ownership Exposure Board fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Copyright Basics, Circular 1 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 027 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ownership Exposure Board can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 027, Ownership Exposure Board: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/027/build-027-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 027, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.", "The problem: Ownership Exposure Board fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Copyright Basics, Circular 1 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 027 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ownership Exposure Board can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 027, Ownership Exposure Board: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Ownership Exposure Board fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 027, 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." }, { "slide": 3, "stage": "System", "copy": [ "POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.", "The problem: Ownership Exposure Board fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Copyright Basics, Circular 1 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 027 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ownership Exposure Board can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 027, Ownership Exposure Board: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Ownership Exposure Board mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 027, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.", "The problem: Ownership Exposure Board fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Copyright Basics, Circular 1 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 027 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ownership Exposure Board can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 027, Ownership Exposure Board: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Copyright Basics, Circular 1 frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Copyright Basics, Circular 1” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Supports recognition of the Copyright Office circular and copyright-basics context; does not establish ownership, registration, infringement, legal advice or RN product outcomes.", "accessibility": "Slide 4 alt text must identify Build 027, 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.copyright.gov/circs/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.", "The problem: Ownership Exposure Board fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Copyright Basics, Circular 1 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 027 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ownership Exposure Board can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 027, Ownership Exposure Board: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 027 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 027, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 027, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.", "The problem: Ownership Exposure Board fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Copyright Basics, Circular 1 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 027 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ownership Exposure Board can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 027, Ownership Exposure Board: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Ownership Exposure Board can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 027, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "POSTING IS NOT OWNERSHIP — A platform can distribute the work without giving you control of the audience, archive, identity, or future access.", "The problem: Ownership Exposure Board fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Copyright Basics, Circular 1 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 027 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ownership Exposure Board can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 027, Ownership Exposure Board: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 027, Ownership Exposure Board: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 027, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 027, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "028", "title": "Ranking Rationale", "template": "RN Builds 4:5 / operations-and-provenance / Build 028", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/replacement-production-covers/build-028-official-excerpt-cover.svg", "altText": "Official NIST AI RMF MANAGE 1 excerpt describing how assessed AI risks are prioritized, responded to and documented using impact, likelihood and available resources.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 32. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/028/build-028-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Ranking Rationale and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 028." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "STORED IS NOT FOUND — A fact can exist in the archive and still fail the person who needs it at the moment of decision.", "The problem: Ranking Rationale fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MANAGE 1 ties prioritization to intended purpose, impact, likelihood, resources and documented residual risk.", "Demo: walk through one bounded state change in the Build 028 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ranking Rationale can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 028, Ranking Rationale: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "STORED IS NOT FOUND — A fact can exist in the archive and still fail the person who needs it at the moment of decision.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/replacement-production-covers/build-028-official-excerpt-cover.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports explaining the dimensions behind a risk ranking; it does not validate Build 028’s ranking method or any particular result.", "accessibility": "Slide 1 alt text must identify Build 028, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 2, "stage": "Problem", "copy": [ "STORED IS NOT FOUND — A fact can exist in the archive and still fail the person who needs it at the moment of decision.", "The problem: Ranking Rationale fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MANAGE 1 ties prioritization to intended purpose, impact, likelihood, resources and documented residual risk.", "Demo: walk through one bounded state change in the Build 028 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ranking Rationale can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 028, Ranking Rationale: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Ranking Rationale fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “STORED IS NOT FOUND — A fact can exist in the archive and still fail the person who needs it at the moment of decision.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 028, 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." }, { "slide": 3, "stage": "System", "copy": [ "STORED IS NOT FOUND — A fact can exist in the archive and still fail the person who needs it at the moment of decision.", "The problem: Ranking Rationale fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MANAGE 1 ties prioritization to intended purpose, impact, likelihood, resources and documented residual risk.", "Demo: walk through one bounded state change in the Build 028 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ranking Rationale can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 028, Ranking Rationale: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Ranking Rationale mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 028, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "STORED IS NOT FOUND — A fact can exist in the archive and still fail the person who needs it at the moment of decision.", "The problem: Ranking Rationale fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MANAGE 1 ties prioritization to intended purpose, impact, likelihood, resources and documented residual risk.", "Demo: walk through one bounded state change in the Build 028 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ranking Rationale can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 028, Ranking Rationale: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: NIST AI RMF MANAGE 1 ties prioritization to intended purpose, impact, likelihood, resources and documented residual risk.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports explaining the dimensions behind a risk ranking; it does not validate Build 028’s ranking method or any particular result.", "accessibility": "Slide 4 alt text must identify Build 028, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 32. Republished courtesy of NIST. NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 5, "stage": "Demo", "copy": [ "STORED IS NOT FOUND — A fact can exist in the archive and still fail the person who needs it at the moment of decision.", "The problem: Ranking Rationale fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MANAGE 1 ties prioritization to intended purpose, impact, likelihood, resources and documented residual risk.", "Demo: walk through one bounded state change in the Build 028 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ranking Rationale can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 028, Ranking Rationale: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 028 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 028, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 028, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "STORED IS NOT FOUND — A fact can exist in the archive and still fail the person who needs it at the moment of decision.", "The problem: Ranking Rationale fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MANAGE 1 ties prioritization to intended purpose, impact, likelihood, resources and documented residual risk.", "Demo: walk through one bounded state change in the Build 028 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ranking Rationale can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 028, Ranking Rationale: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Ranking Rationale can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 028, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "STORED IS NOT FOUND — A fact can exist in the archive and still fail the person who needs it at the moment of decision.", "The problem: Ranking Rationale fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF MANAGE 1 ties prioritization to intended purpose, impact, likelihood, resources and documented residual risk.", "Demo: walk through one bounded state change in the Build 028 prototype. Show the interaction or decision path, not an invented result.", "Implication: Ranking Rationale can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 028, Ranking Rationale: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 028, Ranking Rationale: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 028, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 028, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "029", "title": "Consequence Propagation", "template": "RN Builds 4:5 / operations-and-provenance / Build 029", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/replacement-production-covers/build-029-official-excerpt-cover.svg", "altText": "Official W3C PROV Primer summary describing error checking, tracing responsible parties, regenerating datasets, relating document versions, and inspecting sources and attribution.", "credit": "Copyright © 2013 W3C®. Material reproduced from PROV Model Primer, https://www.w3.org/TR/prov-primer/#summary, under the W3C Document License.", "sourceUrl": "https://www.w3.org/TR/prov-primer/#summary", "rollbackAssetUrl": "/media/builds/029/build-029-linkedin-poster.png" }, "recognizableEntity": { "label": "W3C PROV Primer", "type": "official web standard", "relevance": "W3C PROV Primer is directly relevant to Consequence Propagation and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that World Wide Web Consortium endorses RN or Build 029." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "EVERY CHANGE ENTERS A SYSTEM — A policy edit, model update, data field, or workflow shortcut can alter outcomes far beyond the place it began.", "The problem: Consequence Propagation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV Primer: provenance supports error checking, responsibility tracing, process repetition, version relationships, sources and attribution.", "Demo: walk through one bounded state change in the Build 029 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consequence Propagation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 029, Consequence Propagation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "EVERY CHANGE ENTERS A SYSTEM — A policy edit, model update, data field, or workflow shortcut can alter outcomes far beyond the place it began.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/replacement-production-covers/build-029-official-excerpt-cover.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports tracing how outputs, versions, responsible parties and sources relate; it does not demonstrate Build 029’s propagation logic or imply W3C endorsement.", "accessibility": "Slide 1 alt text must identify Build 029, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "W3C Document License; faithful portion with URL, copyright/status notice; logo excluded." }, { "slide": 2, "stage": "Problem", "copy": [ "EVERY CHANGE ENTERS A SYSTEM — A policy edit, model update, data field, or workflow shortcut can alter outcomes far beyond the place it began.", "The problem: Consequence Propagation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV Primer: provenance supports error checking, responsibility tracing, process repetition, version relationships, sources and attribution.", "Demo: walk through one bounded state change in the Build 029 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consequence Propagation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 029, Consequence Propagation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Consequence Propagation fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “EVERY CHANGE ENTERS A SYSTEM — A policy edit, model update, data field, or workflow shortcut can alter outcomes far beyond the place it began.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 029, 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." }, { "slide": 3, "stage": "System", "copy": [ "EVERY CHANGE ENTERS A SYSTEM — A policy edit, model update, data field, or workflow shortcut can alter outcomes far beyond the place it began.", "The problem: Consequence Propagation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV Primer: provenance supports error checking, responsibility tracing, process repetition, version relationships, sources and attribution.", "Demo: walk through one bounded state change in the Build 029 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consequence Propagation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 029, Consequence Propagation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Consequence Propagation mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 029, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "EVERY CHANGE ENTERS A SYSTEM — A policy edit, model update, data field, or workflow shortcut can alter outcomes far beyond the place it began.", "The problem: Consequence Propagation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV Primer: provenance supports error checking, responsibility tracing, process repetition, version relationships, sources and attribution.", "Demo: walk through one bounded state change in the Build 029 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consequence Propagation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 029, Consequence Propagation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: W3C PROV Primer: provenance supports error checking, responsibility tracing, process repetition, version relationships, sources and attribution.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.w3.org/TR/prov-primer/#summary; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports tracing how outputs, versions, responsible parties and sources relate; it does not demonstrate Build 029’s propagation logic or imply W3C endorsement.", "accessibility": "Slide 4 alt text must identify Build 029, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2013 W3C®. Material reproduced from PROV Model Primer, https://www.w3.org/TR/prov-primer/#summary, under the W3C Document License. W3C Document License; faithful portion with URL, copyright/status notice; logo excluded." }, { "slide": 5, "stage": "Demo", "copy": [ "EVERY CHANGE ENTERS A SYSTEM — A policy edit, model update, data field, or workflow shortcut can alter outcomes far beyond the place it began.", "The problem: Consequence Propagation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV Primer: provenance supports error checking, responsibility tracing, process repetition, version relationships, sources and attribution.", "Demo: walk through one bounded state change in the Build 029 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consequence Propagation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 029, Consequence Propagation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 029 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 029, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 029, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "EVERY CHANGE ENTERS A SYSTEM — A policy edit, model update, data field, or workflow shortcut can alter outcomes far beyond the place it began.", "The problem: Consequence Propagation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV Primer: provenance supports error checking, responsibility tracing, process repetition, version relationships, sources and attribution.", "Demo: walk through one bounded state change in the Build 029 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consequence Propagation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 029, Consequence Propagation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Consequence Propagation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 029, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "EVERY CHANGE ENTERS A SYSTEM — A policy edit, model update, data field, or workflow shortcut can alter outcomes far beyond the place it began.", "The problem: Consequence Propagation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV Primer: provenance supports error checking, responsibility tracing, process repetition, version relationships, sources and attribution.", "Demo: walk through one bounded state change in the Build 029 prototype. Show the interaction or decision path, not an invented result.", "Implication: Consequence Propagation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 029, Consequence Propagation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 029, Consequence Propagation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 029, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 029, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "030", "title": "Interface Repair in Motion", "template": "RN Builds 4:5 / operations-and-provenance / Build 030", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/source-excerpts/build-030-source-excerpt-hold.svg", "altText": "Sequential text composite from the immutable 5 October 2023 WCAG 2.2 Recommendation: title and status, one abstract sentence, then a separately labeled principles passage.", "credit": "Copyright © 2023 W3C®. Excerpt under the 2023 W3C Document License: https://www.w3.org/copyright/document-license-2023/", "sourceUrl": "https://www.w3.org/TR/2023/REC-WCAG22-20231005/", "rollbackAssetUrl": "/media/builds/030/build-030-linkedin-poster.png" }, "recognizableEntity": { "label": "WCAG 2.2", "type": "official web standard", "relevance": "WCAG 2.2 is directly relevant to Interface Repair in Motion and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that World Wide Web Consortium endorses RN or Build 030." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "PASSING A CHECKLIST IS NOT AN INCLUSIVE EXPERIENCE — A screen can satisfy isolated rules while real people still cannot perceive, understand, navigate, recover, or finish.", "The problem: Interface Repair in Motion fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: WCAG 2.2 — immutable 2023 Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 030 prototype. Show the interaction or decision path, not an invented result.", "Implication: Interface Repair in Motion can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 030, Interface Repair in Motion: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "PASSING A CHECKLIST IS NOT AN INCLUSIVE EXPERIENCE — A screen can satisfy isolated rules while real people still cannot perceive, understand, navigate, recover, or finish.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/source-excerpts/build-030-source-excerpt-hold.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 1 alt text must identify Build 030, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2023 W3C®. 2023 W3C Document License: https://www.w3.org/copyright/document-license-2023/" }, { "slide": 2, "stage": "Problem", "copy": [ "PASSING A CHECKLIST IS NOT AN INCLUSIVE EXPERIENCE — A screen can satisfy isolated rules while real people still cannot perceive, understand, navigate, recover, or finish.", "The problem: Interface Repair in Motion fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: WCAG 2.2 — immutable 2023 Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 030 prototype. Show the interaction or decision path, not an invented result.", "Implication: Interface Repair in Motion can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 030, Interface Repair in Motion: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Interface Repair in Motion fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “PASSING A CHECKLIST IS NOT AN INCLUSIVE EXPERIENCE — A screen can satisfy isolated rules while real people still cannot perceive, understand, navigate, recover, or finish.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 030, 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." }, { "slide": 3, "stage": "System", "copy": [ "PASSING A CHECKLIST IS NOT AN INCLUSIVE EXPERIENCE — A screen can satisfy isolated rules while real people still cannot perceive, understand, navigate, recover, or finish.", "The problem: Interface Repair in Motion fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: WCAG 2.2 — immutable 2023 Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 030 prototype. Show the interaction or decision path, not an invented result.", "Implication: Interface Repair in Motion can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 030, Interface Repair in Motion: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Interface Repair in Motion mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 030, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "PASSING A CHECKLIST IS NOT AN INCLUSIVE EXPERIENCE — A screen can satisfy isolated rules while real people still cannot perceive, understand, navigate, recover, or finish.", "The problem: Interface Repair in Motion fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: WCAG 2.2 — immutable 2023 Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 030 prototype. Show the interaction or decision path, not an invented result.", "Implication: Interface Repair in Motion can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 030, Interface Repair in Motion: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: WCAG 2.2 — immutable 2023 Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.w3.org/TR/2023/REC-WCAG22-20231005/; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 030, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2023 W3C®. Excerpt under the 2023 W3C Document License: https://www.w3.org/copyright/document-license-2023/ Copyright © 2023 W3C®. 2023 W3C Document License: https://www.w3.org/copyright/document-license-2023/" }, { "slide": 5, "stage": "Demo", "copy": [ "PASSING A CHECKLIST IS NOT AN INCLUSIVE EXPERIENCE — A screen can satisfy isolated rules while real people still cannot perceive, understand, navigate, recover, or finish.", "The problem: Interface Repair in Motion fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: WCAG 2.2 — immutable 2023 Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 030 prototype. Show the interaction or decision path, not an invented result.", "Implication: Interface Repair in Motion can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 030, Interface Repair in Motion: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 030 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 030, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 030, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "PASSING A CHECKLIST IS NOT AN INCLUSIVE EXPERIENCE — A screen can satisfy isolated rules while real people still cannot perceive, understand, navigate, recover, or finish.", "The problem: Interface Repair in Motion fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: WCAG 2.2 — immutable 2023 Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 030 prototype. Show the interaction or decision path, not an invented result.", "Implication: Interface Repair in Motion can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 030, Interface Repair in Motion: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Interface Repair in Motion can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 030, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "PASSING A CHECKLIST IS NOT AN INCLUSIVE EXPERIENCE — A screen can satisfy isolated rules while real people still cannot perceive, understand, navigate, recover, or finish.", "The problem: Interface Repair in Motion fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: WCAG 2.2 — immutable 2023 Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 030 prototype. Show the interaction or decision path, not an invented result.", "Implication: Interface Repair in Motion can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 030, Interface Repair in Motion: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 030, Interface Repair in Motion: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 030, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 030, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "031", "title": "Telemetry Privacy Field", "template": "RN Builds 4:5 / operations-and-provenance / Build 031", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/production-source-context/build-031-official-source-context.svg", "altText": "Official Version 1.0 title-page text, selected as contextual evidence for Build 031, Telemetry Privacy Field. Production source-context derivative; not evidence of prototype performance or institutional endorsement.", "credit": "NIST (2020), NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0. Republished courtesy of NIST.", "sourceUrl": "https://www.nist.gov/privacy-framework/privacy-framework", "rollbackAssetUrl": "/media/builds/031/build-031-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST Privacy Framework v1.0", "type": "official technical publication", "relevance": "NIST Privacy Framework v1.0 is directly relevant to Telemetry Privacy Field and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 031." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A PRIVACY POLICY IS NOT PRODUCT BEHAVIOR — The real privacy posture appears in defaults, data flows, permissions, retention, inference, sharing, deletion, and failure states.", "The problem: Telemetry Privacy Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST Privacy Framework 1.0, shown as privacy-risk context.", "Demo: walk through one bounded state change in the Build 031 prototype. Show the interaction or decision path, not an invented result.", "Implication: Telemetry Privacy Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 031, Telemetry Privacy Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A PRIVACY POLICY IS NOT PRODUCT BEHAVIOR — The real privacy posture appears in defaults, data flows, permissions, retention, inference, sharing, deletion, and failure states.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/production-source-context/build-031-official-source-context.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 031, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST public information · no endorsement" }, { "slide": 2, "stage": "Problem", "copy": [ "A PRIVACY POLICY IS NOT PRODUCT BEHAVIOR — The real privacy posture appears in defaults, data flows, permissions, retention, inference, sharing, deletion, and failure states.", "The problem: Telemetry Privacy Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST Privacy Framework 1.0, shown as privacy-risk context.", "Demo: walk through one bounded state change in the Build 031 prototype. Show the interaction or decision path, not an invented result.", "Implication: Telemetry Privacy Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 031, Telemetry Privacy Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Telemetry Privacy Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A PRIVACY POLICY IS NOT PRODUCT BEHAVIOR — The real privacy posture appears in defaults, data flows, permissions, retention, inference, sharing, deletion, and failure states.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 031, 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." }, { "slide": 3, "stage": "System", "copy": [ "A PRIVACY POLICY IS NOT PRODUCT BEHAVIOR — The real privacy posture appears in defaults, data flows, permissions, retention, inference, sharing, deletion, and failure states.", "The problem: Telemetry Privacy Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST Privacy Framework 1.0, shown as privacy-risk context.", "Demo: walk through one bounded state change in the Build 031 prototype. Show the interaction or decision path, not an invented result.", "Implication: Telemetry Privacy Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 031, Telemetry Privacy Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Telemetry Privacy Field mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 031, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A PRIVACY POLICY IS NOT PRODUCT BEHAVIOR — The real privacy posture appears in defaults, data flows, permissions, retention, inference, sharing, deletion, and failure states.", "The problem: Telemetry Privacy Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST Privacy Framework 1.0, shown as privacy-risk context.", "Demo: walk through one bounded state change in the Build 031 prototype. Show the interaction or decision path, not an invented result.", "Implication: Telemetry Privacy Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 031, Telemetry Privacy Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: Official NIST Privacy Framework 1.0, shown as privacy-risk context.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.nist.gov/privacy-framework/privacy-framework; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports recognition of the named NIST publication as bounded source context only; does not prove RN prototype performance, compliance, safety, effectiveness, or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 031, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST (2020), NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0. Republished courtesy of NIST. NIST public information · no endorsement" }, { "slide": 5, "stage": "Demo", "copy": [ "A PRIVACY POLICY IS NOT PRODUCT BEHAVIOR — The real privacy posture appears in defaults, data flows, permissions, retention, inference, sharing, deletion, and failure states.", "The problem: Telemetry Privacy Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST Privacy Framework 1.0, shown as privacy-risk context.", "Demo: walk through one bounded state change in the Build 031 prototype. Show the interaction or decision path, not an invented result.", "Implication: Telemetry Privacy Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 031, Telemetry Privacy Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 031 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 031, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 031, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A PRIVACY POLICY IS NOT PRODUCT BEHAVIOR — The real privacy posture appears in defaults, data flows, permissions, retention, inference, sharing, deletion, and failure states.", "The problem: Telemetry Privacy Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST Privacy Framework 1.0, shown as privacy-risk context.", "Demo: walk through one bounded state change in the Build 031 prototype. Show the interaction or decision path, not an invented result.", "Implication: Telemetry Privacy Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 031, Telemetry Privacy Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Telemetry Privacy Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 031, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A PRIVACY POLICY IS NOT PRODUCT BEHAVIOR — The real privacy posture appears in defaults, data flows, permissions, retention, inference, sharing, deletion, and failure states.", "The problem: Telemetry Privacy Field fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Official NIST Privacy Framework 1.0, shown as privacy-risk context.", "Demo: walk through one bounded state change in the Build 031 prototype. Show the interaction or decision path, not an invented result.", "Implication: Telemetry Privacy Field can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 031, Telemetry Privacy Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 031, Telemetry Privacy Field: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 031, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 031, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "032", "title": "Release Blocker Door", "template": "RN Builds 4:5 / operations-and-provenance / Build 032", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/replacement-production-covers/build-032-official-excerpt-cover.svg", "altText": "Official NIST AI RMF excerpts requiring a proceed-or-stop determination and mechanisms to supersede, disengage or deactivate systems with outcomes inconsistent with intended use.", "credit": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 32. Republished courtesy of NIST.", "sourceUrl": "https://doi.org/10.6028/NIST.AI.100-1", "rollbackAssetUrl": "/media/builds/032/build-032-linkedin-poster.png" }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Release Blocker Door and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 032." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A PASSING SCORE DOES NOT AUTHORIZE RELEASE — Consequential AI needs inspectable evidence that the use, workflow, people, vendor, data, and operating controls can hold under pressure.", "The problem: Release Blocker Door fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF release boundary: decide whether deployment should proceed and deactivate systems whose outcomes conflict with intended use.", "Demo: walk through one bounded state change in the Build 032 prototype. Show the interaction or decision path, not an invented result.", "Implication: Release Blocker Door can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 032, Release Blocker Door: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A PASSING SCORE DOES NOT AUTHORIZE RELEASE — Consequential AI needs inspectable evidence that the use, workflow, people, vendor, data, and operating controls can hold under pressure.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/replacement-production-covers/build-032-official-excerpt-cover.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports a go/no-go and deactivate release boundary; it does not certify Build 032’s blocker logic or any release decision.", "accessibility": "Slide 1 alt text must identify Build 032, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 2, "stage": "Problem", "copy": [ "A PASSING SCORE DOES NOT AUTHORIZE RELEASE — Consequential AI needs inspectable evidence that the use, workflow, people, vendor, data, and operating controls can hold under pressure.", "The problem: Release Blocker Door fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF release boundary: decide whether deployment should proceed and deactivate systems whose outcomes conflict with intended use.", "Demo: walk through one bounded state change in the Build 032 prototype. Show the interaction or decision path, not an invented result.", "Implication: Release Blocker Door can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 032, Release Blocker Door: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Release Blocker Door fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A PASSING SCORE DOES NOT AUTHORIZE RELEASE — Consequential AI needs inspectable evidence that the use, workflow, people, vendor, data, and operating controls can hold under pressure.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 032, 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." }, { "slide": 3, "stage": "System", "copy": [ "A PASSING SCORE DOES NOT AUTHORIZE RELEASE — Consequential AI needs inspectable evidence that the use, workflow, people, vendor, data, and operating controls can hold under pressure.", "The problem: Release Blocker Door fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF release boundary: decide whether deployment should proceed and deactivate systems whose outcomes conflict with intended use.", "Demo: walk through one bounded state change in the Build 032 prototype. Show the interaction or decision path, not an invented result.", "Implication: Release Blocker Door can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 032, Release Blocker Door: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Release Blocker Door mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 032, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A PASSING SCORE DOES NOT AUTHORIZE RELEASE — Consequential AI needs inspectable evidence that the use, workflow, people, vendor, data, and operating controls can hold under pressure.", "The problem: Release Blocker Door fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF release boundary: decide whether deployment should proceed and deactivate systems whose outcomes conflict with intended use.", "Demo: walk through one bounded state change in the Build 032 prototype. Show the interaction or decision path, not an invented result.", "Implication: Release Blocker Door can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 032, Release Blocker Door: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: NIST AI RMF release boundary: decide whether deployment should proceed and deactivate systems whose outcomes conflict with intended use.", "visualGuidance": "Use only the recorded official source-context treatment from https://doi.org/10.6028/NIST.AI.100-1; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "Supports a go/no-go and deactivate release boundary; it does not certify Build 032’s blocker logic or any release decision.", "accessibility": "Slide 4 alt text must identify Build 032, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Tabassi, E. (2023), Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, p. 32. Republished courtesy of NIST. NIST-authored technical-series text; citation retained; insignia and third-party material excluded." }, { "slide": 5, "stage": "Demo", "copy": [ "A PASSING SCORE DOES NOT AUTHORIZE RELEASE — Consequential AI needs inspectable evidence that the use, workflow, people, vendor, data, and operating controls can hold under pressure.", "The problem: Release Blocker Door fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF release boundary: decide whether deployment should proceed and deactivate systems whose outcomes conflict with intended use.", "Demo: walk through one bounded state change in the Build 032 prototype. Show the interaction or decision path, not an invented result.", "Implication: Release Blocker Door can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 032, Release Blocker Door: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 032 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 032, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 032, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A PASSING SCORE DOES NOT AUTHORIZE RELEASE — Consequential AI needs inspectable evidence that the use, workflow, people, vendor, data, and operating controls can hold under pressure.", "The problem: Release Blocker Door fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF release boundary: decide whether deployment should proceed and deactivate systems whose outcomes conflict with intended use.", "Demo: walk through one bounded state change in the Build 032 prototype. Show the interaction or decision path, not an invented result.", "Implication: Release Blocker Door can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 032, Release Blocker Door: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Release Blocker Door can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 032, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A PASSING SCORE DOES NOT AUTHORIZE RELEASE — Consequential AI needs inspectable evidence that the use, workflow, people, vendor, data, and operating controls can hold under pressure.", "The problem: Release Blocker Door fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF release boundary: decide whether deployment should proceed and deactivate systems whose outcomes conflict with intended use.", "Demo: walk through one bounded state change in the Build 032 prototype. Show the interaction or decision path, not an invented result.", "Implication: Release Blocker Door can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 032, Release Blocker Door: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 032, Release Blocker Door: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 032, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 032, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "033", "title": "Attack Graph", "template": "RN Builds 4:5 / operations-and-provenance / Build 033", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/033/build-033-linkedin-poster.png", "altText": "Build 033, Attack Graph. Creator-owned 4:5 typographic opening frame. Visible text: “TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST AI Risk Management Framework 1.0", "type": "official technical publication", "relevance": "NIST AI Risk Management Framework 1.0 is directly relevant to Attack Graph and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 033." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.", "The problem: Attack Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 033 prototype. Show the interaction or decision path, not an invented result.", "Implication: Attack Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 033, Attack Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/033/build-033-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 033, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.", "The problem: Attack Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 033 prototype. Show the interaction or decision path, not an invented result.", "Implication: Attack Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 033, Attack Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Attack Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 033, 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." }, { "slide": 3, "stage": "System", "copy": [ "TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.", "The problem: Attack Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 033 prototype. Show the interaction or decision path, not an invented result.", "Implication: Attack Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 033, Attack Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Attack Graph mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 033, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.", "The problem: Attack Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 033 prototype. Show the interaction or decision path, not an invented result.", "Implication: Attack Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 033, Attack Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST AI Risk Management Framework 1.0” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Supports recognition of NIST AI Risk Management Framework 1.0 and the limited source context adjacent to Build 033; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 033, 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://doi.org/10.6028/NIST.AI.100-1; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.", "The problem: Attack Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 033 prototype. Show the interaction or decision path, not an invented result.", "Implication: Attack Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 033, Attack Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 033 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 033, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 033, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.", "The problem: Attack Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 033 prototype. Show the interaction or decision path, not an invented result.", "Implication: Attack Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 033, Attack Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Attack Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 033, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "TEST THE SYSTEM WITHOUT TEACHING THE ATTACK — Defensive exploration should expose weak assumptions, controls, and recovery paths while withholding reusable harmful instructions.", "The problem: Attack Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework 1.0 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 033 prototype. Show the interaction or decision path, not an invented result.", "Implication: Attack Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 033, Attack Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 033, Attack Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 033, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 033, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "034", "title": "Incident Replay Graph", "template": "RN Builds 4:5 / operations-and-provenance / Build 034", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/034/build-034-linkedin-poster.png", "altText": "Build 034, Incident Replay Graph. Creator-owned 4:5 typographic opening frame. Visible text: “THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST SP 800-61 Rev. 3", "type": "official technical publication", "relevance": "NIST SP 800-61 Rev. 3 is directly relevant to Incident Replay Graph and offers professional recognition through an authoritative primary document, not fame or clickbait.", "authorizationBoundary": "Use only the exact document treatment under its recorded terms. Exclude logos, seals, people and third-party material; attribution does not imply that National Institute of Standards and Technology endorses RN or Build 034." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.", "The problem: Incident Replay Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST SP 800-61 Rev. 3 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 034 prototype. Show the interaction or decision path, not an invented result.", "Implication: Incident Replay Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 034, Incident Replay Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/034/build-034-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 034, 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." }, { "slide": 2, "stage": "Problem", "copy": [ "THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.", "The problem: Incident Replay Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST SP 800-61 Rev. 3 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 034 prototype. Show the interaction or decision path, not an invented result.", "Implication: Incident Replay Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 034, Incident Replay Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Incident Replay Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 034, 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." }, { "slide": 3, "stage": "System", "copy": [ "THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.", "The problem: Incident Replay Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST SP 800-61 Rev. 3 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 034 prototype. Show the interaction or decision path, not an invented result.", "Implication: Incident Replay Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 034, Incident Replay Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Incident Replay Graph mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 034, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.", "The problem: Incident Replay Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST SP 800-61 Rev. 3 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 034 prototype. Show the interaction or decision path, not an invented result.", "Implication: Incident Replay Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 034, Incident Replay Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: NIST SP 800-61 Rev. 3 frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST SP 800-61 Rev. 3” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Supports recognition of NIST SP 800-61 Rev. 3 and the limited source context adjacent to Build 034; it does not prove RN's prototype performance, compliance, safety, effectiveness or institutional endorsement.", "accessibility": "Slide 4 alt text must identify Build 034, 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://doi.org/10.6028/NIST.SP.800-61r3; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.", "The problem: Incident Replay Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST SP 800-61 Rev. 3 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 034 prototype. Show the interaction or decision path, not an invented result.", "Implication: Incident Replay Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 034, Incident Replay Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 034 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 034, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 034, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.", "The problem: Incident Replay Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST SP 800-61 Rev. 3 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 034 prototype. Show the interaction or decision path, not an invented result.", "Implication: Incident Replay Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 034, Incident Replay Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Incident Replay Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 034, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THE FAILURE IS MORE THAN THE ERROR MESSAGE — An AI incident includes what happened, who was affected, how the workflow responded, what evidence survived, and whether harm can recur.", "The problem: Incident Replay Graph fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST SP 800-61 Rev. 3 frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 034 prototype. Show the interaction or decision path, not an invented result.", "Implication: Incident Replay Graph can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 034, Incident Replay Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 034, Incident Replay Graph: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 034, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 034, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "035", "title": "An export button is not an exit", "template": "RN Builds 4:5 / AI-and-product-governance / Build 035", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/035/build-035-linkedin-poster.png", "altText": "Build 035, An export button is not an exit. Creator-owned 4:5 typographic opening frame. Visible text: “An export button is not an exit. Test whether exported data creates usable independence.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "European Union / EUR-Lex", "type": "law and issuing institution", "relevance": "European Union / EUR-Lex is a directly relevant contextual authority or primary-source anchor for An export button is not an exit; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: European Union / EUR-Lex is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "An export button is not an exit. Test whether exported data creates usable independence.", "The problem: An export button is not an exit fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 035 prototype. Show the interaction or decision path, not an invented result.", "Implication: An export button is not an exit can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 035, An export button is not an exit: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "An export button is not an exit. Test whether exported data creates usable independence.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/035/build-035-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 035, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "An export button is not an exit. Test whether exported data creates usable independence.", "The problem: An export button is not an exit fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 035 prototype. Show the interaction or decision path, not an invented result.", "Implication: An export button is not an exit can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 035, An export button is not an exit: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: An export button is not an exit fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “An export button is not an exit. Test whether exported data creates usable independence.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 035, 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." }, { "slide": 3, "stage": "System", "copy": [ "An export button is not an exit. Test whether exported data creates usable independence.", "The problem: An export button is not an exit fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 035 prototype. Show the interaction or decision path, not an invented result.", "Implication: An export button is not an exit can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 035, An export button is not an exit: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the An export button is not an exit mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 035, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "An export button is not an exit. Test whether exported data creates usable independence.", "The problem: An export button is not an exit fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 035 prototype. Show the interaction or decision path, not an invented result.", "Implication: An export button is not an exit can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 035, An export button is not an exit: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “European Union / EUR-Lex” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 035, 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://eur-lex.europa.eu/eli/reg/2016/679/oj; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "An export button is not an exit. Test whether exported data creates usable independence.", "The problem: An export button is not an exit fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 035 prototype. Show the interaction or decision path, not an invented result.", "Implication: An export button is not an exit can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 035, An export button is not an exit: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 035 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 035, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 035, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "An export button is not an exit. Test whether exported data creates usable independence.", "The problem: An export button is not an exit fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 035 prototype. Show the interaction or decision path, not an invented result.", "Implication: An export button is not an exit can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 035, An export button is not an exit: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: An export button is not an exit can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 035, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "An export button is not an exit. Test whether exported data creates usable independence.", "The problem: An export button is not an exit fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 035 prototype. Show the interaction or decision path, not an invented result.", "Implication: An export button is not an exit can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 035, An export button is not an exit: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 035, An export button is not an exit: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 035, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 035, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "036", "title": "Offline is a product state", "template": "RN Builds 4:5 / AI-and-product-governance / Build 036", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/source-excerpts/build-036-source-excerpt-hold.svg", "altText": "Sequential text excerpt containing the title, 19 November 2019 Candidate Recommendation status, and offline-capability motivation passage from Service Workers 1.", "credit": "Copyright © 2019 W3C®. Excerpt under the W3C Software and Document License linked by the snapshot: https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document", "sourceUrl": "https://www.w3.org/TR/2019/CR-service-workers-1-20191119/", "rollbackAssetUrl": "/media/builds/036/build-036-linkedin-poster.png" }, "recognizableEntity": { "label": "W3C", "type": "technical standard", "relevance": "W3C is a directly relevant contextual authority or primary-source anchor for Offline is a product state; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: W3C is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Offline is a product state. Keep essential work safe through disconnection and recovery.", "The problem: Offline is a product state fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Service Workers 1 — 2019 Candidate Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 036 prototype. Show the interaction or decision path, not an invented result.", "Implication: Offline is a product state can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 036, Offline is a product state: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Offline is a product state. Keep essential work safe through disconnection and recovery.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/source-excerpts/build-036-source-excerpt-hold.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 1 alt text must identify Build 036, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2019 W3C®. W3C Software and Document License linked by the snapshot: https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document" }, { "slide": 2, "stage": "Problem", "copy": [ "Offline is a product state. Keep essential work safe through disconnection and recovery.", "The problem: Offline is a product state fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Service Workers 1 — 2019 Candidate Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 036 prototype. Show the interaction or decision path, not an invented result.", "Implication: Offline is a product state can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 036, Offline is a product state: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Offline is a product state fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Offline is a product state. Keep essential work safe through disconnection and recovery.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 036, 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." }, { "slide": 3, "stage": "System", "copy": [ "Offline is a product state. Keep essential work safe through disconnection and recovery.", "The problem: Offline is a product state fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Service Workers 1 — 2019 Candidate Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 036 prototype. Show the interaction or decision path, not an invented result.", "Implication: Offline is a product state can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 036, Offline is a product state: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Offline is a product state mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 036, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Offline is a product state. Keep essential work safe through disconnection and recovery.", "The problem: Offline is a product state fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Service Workers 1 — 2019 Candidate Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 036 prototype. Show the interaction or decision path, not an invented result.", "Implication: Offline is a product state can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 036, Offline is a product state: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: Service Workers 1 — 2019 Candidate Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.w3.org/TR/2019/CR-service-workers-1-20191119/; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 036, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2019 W3C®. Excerpt under the W3C Software and Document License linked by the snapshot: https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document Copyright © 2019 W3C®. W3C Software and Document License linked by the snapshot: https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document" }, { "slide": 5, "stage": "Demo", "copy": [ "Offline is a product state. Keep essential work safe through disconnection and recovery.", "The problem: Offline is a product state fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Service Workers 1 — 2019 Candidate Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 036 prototype. Show the interaction or decision path, not an invented result.", "Implication: Offline is a product state can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 036, Offline is a product state: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 036 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 036, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 036, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Offline is a product state. Keep essential work safe through disconnection and recovery.", "The problem: Offline is a product state fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Service Workers 1 — 2019 Candidate Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 036 prototype. Show the interaction or decision path, not an invented result.", "Implication: Offline is a product state can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 036, Offline is a product state: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Offline is a product state can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 036, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Offline is a product state. Keep essential work safe through disconnection and recovery.", "The problem: Offline is a product state fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: Service Workers 1 — 2019 Candidate Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 036 prototype. Show the interaction or decision path, not an invented result.", "Implication: Offline is a product state can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 036, Offline is a product state: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 036, Offline is a product state: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 036, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 036, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "037", "title": "Feedback is a signal, not a command", "template": "RN Builds 4:5 / AI-and-product-governance / Build 037", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/037/build-037-linkedin-poster.png", "altText": "Build 037, Feedback is a signal, not a command. Creator-owned 4:5 typographic opening frame. Visible text: “Feedback is a signal, not a command. Turn feedback into governed evidence for change.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "risk-management framework", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for Feedback is a signal, not a command; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Feedback is a signal, not a command. Turn feedback into governed evidence for change.", "The problem: Feedback is a signal, not a command fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 037 prototype. Show the interaction or decision path, not an invented result.", "Implication: Feedback is a signal, not a command can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 037, Feedback is a signal, not a command: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Feedback is a signal, not a command. Turn feedback into governed evidence for change.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/037/build-037-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 037, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "Feedback is a signal, not a command. Turn feedback into governed evidence for change.", "The problem: Feedback is a signal, not a command fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 037 prototype. Show the interaction or decision path, not an invented result.", "Implication: Feedback is a signal, not a command can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 037, Feedback is a signal, not a command: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Feedback is a signal, not a command fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Feedback is a signal, not a command. Turn feedback into governed evidence for change.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 037, 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." }, { "slide": 3, "stage": "System", "copy": [ "Feedback is a signal, not a command. Turn feedback into governed evidence for change.", "The problem: Feedback is a signal, not a command fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 037 prototype. Show the interaction or decision path, not an invented result.", "Implication: Feedback is a signal, not a command can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 037, Feedback is a signal, not a command: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Feedback is a signal, not a command mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 037, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Feedback is a signal, not a command. Turn feedback into governed evidence for change.", "The problem: Feedback is a signal, not a command fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 037 prototype. Show the interaction or decision path, not an invented result.", "Implication: Feedback is a signal, not a command can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 037, Feedback is a signal, not a command: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “National Institute of Standards and Technology” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 037, 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://doi.org/10.6028/NIST.AI.100-1; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Feedback is a signal, not a command. Turn feedback into governed evidence for change.", "The problem: Feedback is a signal, not a command fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 037 prototype. Show the interaction or decision path, not an invented result.", "Implication: Feedback is a signal, not a command can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 037, Feedback is a signal, not a command: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 037 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 037, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 037, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Feedback is a signal, not a command. Turn feedback into governed evidence for change.", "The problem: Feedback is a signal, not a command fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 037 prototype. Show the interaction or decision path, not an invented result.", "Implication: Feedback is a signal, not a command can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 037, Feedback is a signal, not a command: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Feedback is a signal, not a command can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 037, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Feedback is a signal, not a command. Turn feedback into governed evidence for change.", "The problem: Feedback is a signal, not a command fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 037 prototype. Show the interaction or decision path, not an invented result.", "Implication: Feedback is a signal, not a command can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 037, Feedback is a signal, not a command: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 037, Feedback is a signal, not a command: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 037, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 037, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "038", "title": "A benchmark is not performance", "template": "RN Builds 4:5 / AI-and-product-governance / Build 038", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/038/build-038-linkedin-poster.png", "altText": "Build 038, A benchmark is not performance. Creator-owned 4:5 typographic opening frame. Visible text: “A benchmark is not performance. Evaluate AI inside the domain and decision that matter.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "risk-management framework", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for A benchmark is not performance; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A benchmark is not performance. Evaluate AI inside the domain and decision that matter.", "The problem: A benchmark is not performance fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 038 prototype. Show the interaction or decision path, not an invented result.", "Implication: A benchmark is not performance can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 038, A benchmark is not performance: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A benchmark is not performance. Evaluate AI inside the domain and decision that matter.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/038/build-038-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 038, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A benchmark is not performance. Evaluate AI inside the domain and decision that matter.", "The problem: A benchmark is not performance fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 038 prototype. Show the interaction or decision path, not an invented result.", "Implication: A benchmark is not performance can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 038, A benchmark is not performance: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: A benchmark is not performance fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A benchmark is not performance. Evaluate AI inside the domain and decision that matter.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 038, 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." }, { "slide": 3, "stage": "System", "copy": [ "A benchmark is not performance. Evaluate AI inside the domain and decision that matter.", "The problem: A benchmark is not performance fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 038 prototype. Show the interaction or decision path, not an invented result.", "Implication: A benchmark is not performance can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 038, A benchmark is not performance: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the A benchmark is not performance mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 038, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A benchmark is not performance. Evaluate AI inside the domain and decision that matter.", "The problem: A benchmark is not performance fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 038 prototype. Show the interaction or decision path, not an invented result.", "Implication: A benchmark is not performance can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 038, A benchmark is not performance: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “National Institute of Standards and Technology” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 038, 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://doi.org/10.6028/NIST.AI.100-1; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A benchmark is not performance. Evaluate AI inside the domain and decision that matter.", "The problem: A benchmark is not performance fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 038 prototype. Show the interaction or decision path, not an invented result.", "Implication: A benchmark is not performance can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 038, A benchmark is not performance: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 038 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 038, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 038, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A benchmark is not performance. Evaluate AI inside the domain and decision that matter.", "The problem: A benchmark is not performance fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 038 prototype. Show the interaction or decision path, not an invented result.", "Implication: A benchmark is not performance can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 038, A benchmark is not performance: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: A benchmark is not performance can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 038, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A benchmark is not performance. Evaluate AI inside the domain and decision that matter.", "The problem: A benchmark is not performance fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 038 prototype. Show the interaction or decision path, not an invented result.", "Implication: A benchmark is not performance can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 038, A benchmark is not performance: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 038, A benchmark is not performance: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 038, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 038, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "039", "title": "A trace is evidence, not truth", "template": "RN Builds 4:5 / AI-and-product-governance / Build 039", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/039/build-039-linkedin-poster.png", "altText": "Build 039, A trace is evidence, not truth. Creator-owned 4:5 typographic opening frame. Visible text: “A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "W3C", "type": "provenance standard", "relevance": "W3C is a directly relevant contextual authority or primary-source anchor for A trace is evidence, not truth; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: W3C is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.", "The problem: A trace is evidence, not truth fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 039 prototype. Show the interaction or decision path, not an invented result.", "Implication: A trace is evidence, not truth can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 039, A trace is evidence, not truth: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/039/build-039-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 039, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.", "The problem: A trace is evidence, not truth fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 039 prototype. Show the interaction or decision path, not an invented result.", "Implication: A trace is evidence, not truth can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 039, A trace is evidence, not truth: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: A trace is evidence, not truth fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 039, 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." }, { "slide": 3, "stage": "System", "copy": [ "A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.", "The problem: A trace is evidence, not truth fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 039 prototype. Show the interaction or decision path, not an invented result.", "Implication: A trace is evidence, not truth can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 039, A trace is evidence, not truth: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the A trace is evidence, not truth mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 039, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.", "The problem: A trace is evidence, not truth fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 039 prototype. Show the interaction or decision path, not an invented result.", "Implication: A trace is evidence, not truth can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 039, A trace is evidence, not truth: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: W3C frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “W3C” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 039, 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/2013/REC-prov-o-20130430/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.", "The problem: A trace is evidence, not truth fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 039 prototype. Show the interaction or decision path, not an invented result.", "Implication: A trace is evidence, not truth can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 039, A trace is evidence, not truth: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 039 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 039, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 039, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.", "The problem: A trace is evidence, not truth fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 039 prototype. Show the interaction or decision path, not an invented result.", "Implication: A trace is evidence, not truth can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 039, A trace is evidence, not truth: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: A trace is evidence, not truth can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 039, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A trace is evidence, not truth. Inspect agent activity without overstating what logs prove.", "The problem: A trace is evidence, not truth fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: W3C frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 039 prototype. Show the interaction or decision path, not an invented result.", "Implication: A trace is evidence, not truth can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 039, A trace is evidence, not truth: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 039, A trace is evidence, not truth: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 039, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 039, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "040", "title": "Confidence is not permission", "template": "RN Builds 4:5 / AI-and-product-governance / Build 040", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/040/build-040-linkedin-poster.png", "altText": "Build 040, Confidence is not permission. Creator-owned 4:5 typographic opening frame. Visible text: “Confidence is not permission. Stop or escalate when consequence outruns evidence.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "risk-management framework", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for Confidence is not permission; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Confidence is not permission. Stop or escalate when consequence outruns evidence.", "The problem: Confidence is not permission fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 040 prototype. Show the interaction or decision path, not an invented result.", "Implication: Confidence is not permission can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 040, Confidence is not permission: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Confidence is not permission. Stop or escalate when consequence outruns evidence.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/040/build-040-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 040, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "Confidence is not permission. Stop or escalate when consequence outruns evidence.", "The problem: Confidence is not permission fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 040 prototype. Show the interaction or decision path, not an invented result.", "Implication: Confidence is not permission can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 040, Confidence is not permission: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Confidence is not permission fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Confidence is not permission. Stop or escalate when consequence outruns evidence.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 040, 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." }, { "slide": 3, "stage": "System", "copy": [ "Confidence is not permission. Stop or escalate when consequence outruns evidence.", "The problem: Confidence is not permission fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 040 prototype. Show the interaction or decision path, not an invented result.", "Implication: Confidence is not permission can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 040, Confidence is not permission: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Confidence is not permission mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 040, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Confidence is not permission. Stop or escalate when consequence outruns evidence.", "The problem: Confidence is not permission fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 040 prototype. Show the interaction or decision path, not an invented result.", "Implication: Confidence is not permission can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 040, Confidence is not permission: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “National Institute of Standards and Technology” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 040, 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://doi.org/10.6028/NIST.AI.100-1; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Confidence is not permission. Stop or escalate when consequence outruns evidence.", "The problem: Confidence is not permission fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 040 prototype. Show the interaction or decision path, not an invented result.", "Implication: Confidence is not permission can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 040, Confidence is not permission: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 040 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 040, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 040, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Confidence is not permission. Stop or escalate when consequence outruns evidence.", "The problem: Confidence is not permission fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 040 prototype. Show the interaction or decision path, not an invented result.", "Implication: Confidence is not permission can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 040, Confidence is not permission: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Confidence is not permission can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 040, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Confidence is not permission. Stop or escalate when consequence outruns evidence.", "The problem: Confidence is not permission fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 040 prototype. Show the interaction or decision path, not an invented result.", "Implication: Confidence is not permission can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 040, Confidence is not permission: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 040, Confidence is not permission: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 040, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 040, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "041", "title": "AI work needs an owner", "template": "RN Builds 4:5 / AI-and-product-governance / Build 041", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/source-excerpts/build-041-source-excerpt-hold.svg", "altText": "Sequential text composite from NIST AI RMF GOVERN 2 containing the accountability statement and separately labeled subcategories 2.1 and 2.3 about roles and executive responsibility.", "credit": "Official NIST-authored publication excerpt; not subject to copyright in the United States. Third-party material excluded. Policy: https://www.nist.gov/open", "sourceUrl": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf", "rollbackAssetUrl": "/media/builds/041/build-041-linkedin-poster.png" }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "risk-management framework", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for AI work needs an owner; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "AI work needs an owner. Connect every AI decision to accountable ownership.", "The problem: AI work needs an owner fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF 1.0, p. 23. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 041 prototype. Show the interaction or decision path, not an invented result.", "Implication: AI work needs an owner can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 041, AI work needs an owner: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "AI work needs an owner. Connect every AI decision to accountable ownership.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/source-excerpts/build-041-source-excerpt-hold.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 1 alt text must identify Build 041, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Official NIST-authored publication text; not subject to copyright in the United States. Third-party material excluded. NIST open-use policy: https://www.nist.gov/open" }, { "slide": 2, "stage": "Problem", "copy": [ "AI work needs an owner. Connect every AI decision to accountable ownership.", "The problem: AI work needs an owner fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF 1.0, p. 23. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 041 prototype. Show the interaction or decision path, not an invented result.", "Implication: AI work needs an owner can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 041, AI work needs an owner: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: AI work needs an owner fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “AI work needs an owner. Connect every AI decision to accountable ownership.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 041, 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." }, { "slide": 3, "stage": "System", "copy": [ "AI work needs an owner. Connect every AI decision to accountable ownership.", "The problem: AI work needs an owner fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF 1.0, p. 23. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 041 prototype. Show the interaction or decision path, not an invented result.", "Implication: AI work needs an owner can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 041, AI work needs an owner: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the AI work needs an owner mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 041, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "AI work needs an owner. Connect every AI decision to accountable ownership.", "The problem: AI work needs an owner fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF 1.0, p. 23. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 041 prototype. Show the interaction or decision path, not an invented result.", "Implication: AI work needs an owner can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 041, AI work needs an owner: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: NIST AI RMF 1.0, p. 23. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "visualGuidance": "Use only the recorded official source-context treatment from https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 041, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Official NIST-authored publication excerpt; not subject to copyright in the United States. Third-party material excluded. Policy: https://www.nist.gov/open Official NIST-authored publication text; not subject to copyright in the United States. Third-party material excluded. NIST open-use policy: https://www.nist.gov/open" }, { "slide": 5, "stage": "Demo", "copy": [ "AI work needs an owner. Connect every AI decision to accountable ownership.", "The problem: AI work needs an owner fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF 1.0, p. 23. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 041 prototype. Show the interaction or decision path, not an invented result.", "Implication: AI work needs an owner can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 041, AI work needs an owner: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 041 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 041, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 041, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "AI work needs an owner. Connect every AI decision to accountable ownership.", "The problem: AI work needs an owner fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF 1.0, p. 23. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 041 prototype. Show the interaction or decision path, not an invented result.", "Implication: AI work needs an owner can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 041, AI work needs an owner: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: AI work needs an owner can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 041, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "AI work needs an owner. Connect every AI decision to accountable ownership.", "The problem: AI work needs an owner fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: NIST AI RMF 1.0, p. 23. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 041 prototype. Show the interaction or decision path, not an invented result.", "Implication: AI work needs an owner can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 041, AI work needs an owner: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 041, AI work needs an owner: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 041, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 041, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "042", "title": "A prompt is not a job description", "template": "RN Builds 4:5 / AI-and-product-governance / Build 042", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/042/build-042-linkedin-poster.png", "altText": "Build 042, A prompt is not a job description. Creator-owned 4:5 typographic opening frame. Visible text: “A prompt is not a job description. Define purpose, authority, tools and human review.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "risk-management framework", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for A prompt is not a job description; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A prompt is not a job description. Define purpose, authority, tools and human review.", "The problem: A prompt is not a job description fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 042 prototype. Show the interaction or decision path, not an invented result.", "Implication: A prompt is not a job description can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 042, A prompt is not a job description: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A prompt is not a job description. Define purpose, authority, tools and human review.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/042/build-042-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 042, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A prompt is not a job description. Define purpose, authority, tools and human review.", "The problem: A prompt is not a job description fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 042 prototype. Show the interaction or decision path, not an invented result.", "Implication: A prompt is not a job description can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 042, A prompt is not a job description: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: A prompt is not a job description fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A prompt is not a job description. Define purpose, authority, tools and human review.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 042, 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." }, { "slide": 3, "stage": "System", "copy": [ "A prompt is not a job description. Define purpose, authority, tools and human review.", "The problem: A prompt is not a job description fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 042 prototype. Show the interaction or decision path, not an invented result.", "Implication: A prompt is not a job description can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 042, A prompt is not a job description: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the A prompt is not a job description mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 042, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A prompt is not a job description. Define purpose, authority, tools and human review.", "The problem: A prompt is not a job description fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 042 prototype. Show the interaction or decision path, not an invented result.", "Implication: A prompt is not a job description can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 042, A prompt is not a job description: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “National Institute of Standards and Technology” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 042, 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://doi.org/10.6028/NIST.AI.100-1; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A prompt is not a job description. Define purpose, authority, tools and human review.", "The problem: A prompt is not a job description fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 042 prototype. Show the interaction or decision path, not an invented result.", "Implication: A prompt is not a job description can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 042, A prompt is not a job description: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 042 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 042, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 042, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A prompt is not a job description. Define purpose, authority, tools and human review.", "The problem: A prompt is not a job description fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 042 prototype. Show the interaction or decision path, not an invented result.", "Implication: A prompt is not a job description can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 042, A prompt is not a job description: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: A prompt is not a job description can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 042, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A prompt is not a job description. Define purpose, authority, tools and human review.", "The problem: A prompt is not a job description fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 042 prototype. Show the interaction or decision path, not an invented result.", "Implication: A prompt is not a job description can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 042, A prompt is not a job description: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 042, A prompt is not a job description: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 042, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 042, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "043", "title": "More agents create more handoffs", "template": "RN Builds 4:5 / AI-and-product-governance / Build 043", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/043/build-043-linkedin-poster.png", "altText": "Build 043, More agents create more handoffs. Creator-owned 4:5 typographic opening frame. Visible text: “More agents create more handoffs. Coordinate specialized agents without losing context or ownership.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "risk-management framework", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for More agents create more handoffs; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "More agents create more handoffs. Coordinate specialized agents without losing context or ownership.", "The problem: More agents create more handoffs fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 043 prototype. Show the interaction or decision path, not an invented result.", "Implication: More agents create more handoffs can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 043, More agents create more handoffs: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "More agents create more handoffs. Coordinate specialized agents without losing context or ownership.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/043/build-043-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 043, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "More agents create more handoffs. Coordinate specialized agents without losing context or ownership.", "The problem: More agents create more handoffs fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 043 prototype. Show the interaction or decision path, not an invented result.", "Implication: More agents create more handoffs can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 043, More agents create more handoffs: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: More agents create more handoffs fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “More agents create more handoffs. Coordinate specialized agents without losing context or ownership.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 043, 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." }, { "slide": 3, "stage": "System", "copy": [ "More agents create more handoffs. Coordinate specialized agents without losing context or ownership.", "The problem: More agents create more handoffs fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 043 prototype. Show the interaction or decision path, not an invented result.", "Implication: More agents create more handoffs can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 043, More agents create more handoffs: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the More agents create more handoffs mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 043, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "More agents create more handoffs. Coordinate specialized agents without losing context or ownership.", "The problem: More agents create more handoffs fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 043 prototype. Show the interaction or decision path, not an invented result.", "Implication: More agents create more handoffs can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 043, More agents create more handoffs: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “National Institute of Standards and Technology” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 043, 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://doi.org/10.6028/NIST.AI.100-1; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "More agents create more handoffs. Coordinate specialized agents without losing context or ownership.", "The problem: More agents create more handoffs fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 043 prototype. Show the interaction or decision path, not an invented result.", "Implication: More agents create more handoffs can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 043, More agents create more handoffs: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 043 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 043, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 043, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "More agents create more handoffs. Coordinate specialized agents without losing context or ownership.", "The problem: More agents create more handoffs fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 043 prototype. Show the interaction or decision path, not an invented result.", "Implication: More agents create more handoffs can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 043, More agents create more handoffs: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: More agents create more handoffs can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 043, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "More agents create more handoffs. Coordinate specialized agents without losing context or ownership.", "The problem: More agents create more handoffs fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 043 prototype. Show the interaction or decision path, not an invented result.", "Implication: More agents create more handoffs can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 043, More agents create more handoffs: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 043, More agents create more handoffs: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 043, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 043, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "044", "title": "Requirements are not copy-paste blocks", "template": "RN Builds 4:5 / AI-and-product-governance / Build 044", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/044/build-044-linkedin-poster.png", "altText": "Build 044, Requirements are not copy-paste blocks. Creator-owned 4:5 typographic opening frame. Visible text: “Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "European Union / EUR-Lex", "type": "law and issuing institution", "relevance": "European Union / EUR-Lex is a directly relevant contextual authority or primary-source anchor for Requirements are not copy-paste blocks; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: European Union / EUR-Lex is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.", "The problem: Requirements are not copy-paste blocks fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 044 prototype. Show the interaction or decision path, not an invented result.", "Implication: Requirements are not copy-paste blocks can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 044, Requirements are not copy-paste blocks: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/044/build-044-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 044, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.", "The problem: Requirements are not copy-paste blocks fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 044 prototype. Show the interaction or decision path, not an invented result.", "Implication: Requirements are not copy-paste blocks can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 044, Requirements are not copy-paste blocks: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Requirements are not copy-paste blocks fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 044, 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." }, { "slide": 3, "stage": "System", "copy": [ "Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.", "The problem: Requirements are not copy-paste blocks fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 044 prototype. Show the interaction or decision path, not an invented result.", "Implication: Requirements are not copy-paste blocks can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 044, Requirements are not copy-paste blocks: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Requirements are not copy-paste blocks mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 044, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.", "The problem: Requirements are not copy-paste blocks fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 044 prototype. Show the interaction or decision path, not an invented result.", "Implication: Requirements are not copy-paste blocks can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 044, Requirements are not copy-paste blocks: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “European Union / EUR-Lex” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 044, 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://eur-lex.europa.eu/eli/reg/2016/679/oj; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.", "The problem: Requirements are not copy-paste blocks fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 044 prototype. Show the interaction or decision path, not an invented result.", "Implication: Requirements are not copy-paste blocks can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 044, Requirements are not copy-paste blocks: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 044 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 044, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 044, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.", "The problem: Requirements are not copy-paste blocks fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 044 prototype. Show the interaction or decision path, not an invented result.", "Implication: Requirements are not copy-paste blocks can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 044, Requirements are not copy-paste blocks: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Requirements are not copy-paste blocks can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 044, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Requirements are not copy-paste blocks. Reuse regulated structure while preserving legal context.", "The problem: Requirements are not copy-paste blocks fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: European Union / EUR-Lex frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 044 prototype. Show the interaction or decision path, not an invented result.", "Implication: Requirements are not copy-paste blocks can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 044, Requirements are not copy-paste blocks: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 044, Requirements are not copy-paste blocks: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 044, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 044, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "045", "title": "Availability is not access", "template": "RN Builds 4:5 / access-context-and-literacy / Build 045", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/045/build-045-linkedin-poster.png", "altText": "Build 045, Availability is not access. Creator-owned 4:5 typographic opening frame. Visible text: “Availability is not access. Reveal barriers across the full cannabis care journey.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Hawai‘i State Department of Health", "type": "state public-health program", "relevance": "Hawai‘i State Department of Health is a directly relevant contextual authority or primary-source anchor for Availability is not access; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: Hawai‘i State Department of Health is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Availability is not access. Reveal barriers across the full cannabis care journey.", "The problem: Availability is not access fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 045 prototype. Show the interaction or decision path, not an invented result.", "Implication: Availability is not access can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 045, Availability is not access: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Availability is not access. Reveal barriers across the full cannabis care journey.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/045/build-045-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 045, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "Availability is not access. Reveal barriers across the full cannabis care journey.", "The problem: Availability is not access fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 045 prototype. Show the interaction or decision path, not an invented result.", "Implication: Availability is not access can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 045, Availability is not access: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Availability is not access fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Availability is not access. Reveal barriers across the full cannabis care journey.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 045, 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." }, { "slide": 3, "stage": "System", "copy": [ "Availability is not access. Reveal barriers across the full cannabis care journey.", "The problem: Availability is not access fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 045 prototype. Show the interaction or decision path, not an invented result.", "Implication: Availability is not access can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 045, Availability is not access: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Availability is not access mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 045, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Availability is not access. Reveal barriers across the full cannabis care journey.", "The problem: Availability is not access fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 045 prototype. Show the interaction or decision path, not an invented result.", "Implication: Availability is not access can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 045, Availability is not access: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Hawai‘i State Department of Health” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 045, 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://health.hawaii.gov/medicalcannabis/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Availability is not access. Reveal barriers across the full cannabis care journey.", "The problem: Availability is not access fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 045 prototype. Show the interaction or decision path, not an invented result.", "Implication: Availability is not access can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 045, Availability is not access: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 045 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 045, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 045, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Availability is not access. Reveal barriers across the full cannabis care journey.", "The problem: Availability is not access fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 045 prototype. Show the interaction or decision path, not an invented result.", "Implication: Availability is not access can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 045, Availability is not access: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Availability is not access can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 045, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Availability is not access. Reveal barriers across the full cannabis care journey.", "The problem: Availability is not access fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 045 prototype. Show the interaction or decision path, not an invented result.", "Implication: Availability is not access can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 045, Availability is not access: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 045, Availability is not access: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 045, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 045, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "046", "title": "Essential systems cross the shore", "template": "RN Builds 4:5 / access-context-and-literacy / Build 046", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/046/build-046-linkedin-poster.png", "altText": "Build 046, Essential systems cross the shore. Creator-owned 4:5 typographic opening frame. Visible text: “Essential systems cross the shore. Trace island systems through local and external dependencies.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Federal Emergency Management Agency", "type": "federal resilience guidance", "relevance": "Federal Emergency Management Agency is a directly relevant contextual authority or primary-source anchor for Essential systems cross the shore; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: Federal Emergency Management Agency is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Essential systems cross the shore. Trace island systems through local and external dependencies.", "The problem: Essential systems cross the shore fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Emergency Management Agency frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 046 prototype. Show the interaction or decision path, not an invented result.", "Implication: Essential systems cross the shore can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 046, Essential systems cross the shore: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Essential systems cross the shore. Trace island systems through local and external dependencies.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/046/build-046-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 046, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "Essential systems cross the shore. Trace island systems through local and external dependencies.", "The problem: Essential systems cross the shore fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Emergency Management Agency frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 046 prototype. Show the interaction or decision path, not an invented result.", "Implication: Essential systems cross the shore can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 046, Essential systems cross the shore: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Essential systems cross the shore fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Essential systems cross the shore. Trace island systems through local and external dependencies.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 046, 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." }, { "slide": 3, "stage": "System", "copy": [ "Essential systems cross the shore. Trace island systems through local and external dependencies.", "The problem: Essential systems cross the shore fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Emergency Management Agency frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 046 prototype. Show the interaction or decision path, not an invented result.", "Implication: Essential systems cross the shore can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 046, Essential systems cross the shore: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Essential systems cross the shore mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 046, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Essential systems cross the shore. Trace island systems through local and external dependencies.", "The problem: Essential systems cross the shore fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Emergency Management Agency frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 046 prototype. Show the interaction or decision path, not an invented result.", "Implication: Essential systems cross the shore can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 046, Essential systems cross the shore: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Federal Emergency Management Agency frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Federal Emergency Management Agency” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 046, 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.fema.gov/emergency-managers/risk-management/building-science/supply-chain-resilience-guide; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Essential systems cross the shore. Trace island systems through local and external dependencies.", "The problem: Essential systems cross the shore fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Emergency Management Agency frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 046 prototype. Show the interaction or decision path, not an invented result.", "Implication: Essential systems cross the shore can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 046, Essential systems cross the shore: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 046 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 046, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 046, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Essential systems cross the shore. Trace island systems through local and external dependencies.", "The problem: Essential systems cross the shore fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Emergency Management Agency frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 046 prototype. Show the interaction or decision path, not an invented result.", "Implication: Essential systems cross the shore can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 046, Essential systems cross the shore: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Essential systems cross the shore can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 046, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Essential systems cross the shore. Trace island systems through local and external dependencies.", "The problem: Essential systems cross the shore fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Emergency Management Agency frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 046 prototype. Show the interaction or decision path, not an invented result.", "Implication: Essential systems cross the shore can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 046, Essential systems cross the shore: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 046, Essential systems cross the shore: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 046, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 046, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "047", "title": "A good idea is not context-free", "template": "RN Builds 4:5 / access-context-and-literacy / Build 047", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/047/build-047-linkedin-poster.png", "altText": "Build 047, A good idea is not context-free. Creator-owned 4:5 typographic opening frame. Visible text: “A good idea is not context-free. Test whether an intervention fits a different place.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Centers for Disease Control and Prevention", "type": "public-health evaluation framework", "relevance": "Centers for Disease Control and Prevention is a directly relevant contextual authority or primary-source anchor for A good idea is not context-free; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: Centers for Disease Control and Prevention is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A good idea is not context-free. Test whether an intervention fits a different place.", "The problem: A good idea is not context-free fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Centers for Disease Control and Prevention frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 047 prototype. Show the interaction or decision path, not an invented result.", "Implication: A good idea is not context-free can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 047, A good idea is not context-free: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A good idea is not context-free. Test whether an intervention fits a different place.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/047/build-047-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 047, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A good idea is not context-free. Test whether an intervention fits a different place.", "The problem: A good idea is not context-free fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Centers for Disease Control and Prevention frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 047 prototype. Show the interaction or decision path, not an invented result.", "Implication: A good idea is not context-free can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 047, A good idea is not context-free: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: A good idea is not context-free fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A good idea is not context-free. Test whether an intervention fits a different place.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 047, 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." }, { "slide": 3, "stage": "System", "copy": [ "A good idea is not context-free. Test whether an intervention fits a different place.", "The problem: A good idea is not context-free fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Centers for Disease Control and Prevention frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 047 prototype. Show the interaction or decision path, not an invented result.", "Implication: A good idea is not context-free can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 047, A good idea is not context-free: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the A good idea is not context-free mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 047, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A good idea is not context-free. Test whether an intervention fits a different place.", "The problem: A good idea is not context-free fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Centers for Disease Control and Prevention frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 047 prototype. Show the interaction or decision path, not an invented result.", "Implication: A good idea is not context-free can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 047, A good idea is not context-free: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Centers for Disease Control and Prevention frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Centers for Disease Control and Prevention” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 047, 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.cdc.gov/evaluation/php/evaluation-framework/index.html; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A good idea is not context-free. Test whether an intervention fits a different place.", "The problem: A good idea is not context-free fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Centers for Disease Control and Prevention frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 047 prototype. Show the interaction or decision path, not an invented result.", "Implication: A good idea is not context-free can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 047, A good idea is not context-free: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 047 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 047, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 047, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A good idea is not context-free. Test whether an intervention fits a different place.", "The problem: A good idea is not context-free fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Centers for Disease Control and Prevention frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 047 prototype. Show the interaction or decision path, not an invented result.", "Implication: A good idea is not context-free can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 047, A good idea is not context-free: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: A good idea is not context-free can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 047, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A good idea is not context-free. Test whether an intervention fits a different place.", "The problem: A good idea is not context-free fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Centers for Disease Control and Prevention frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 047 prototype. Show the interaction or decision path, not an invented result.", "Implication: A good idea is not context-free can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 047, A good idea is not context-free: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 047, A good idea is not context-free: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 047, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 047, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "048", "title": "The rule and journey differ", "template": "RN Builds 4:5 / access-context-and-literacy / Build 048", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/048/build-048-linkedin-poster.png", "altText": "Build 048, The rule and journey differ. Creator-owned 4:5 typographic opening frame. Visible text: “The rule and journey differ. Compare formal policy with the burden of navigating it.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Hawai‘i State Department of Health", "type": "state public-health program", "relevance": "Hawai‘i State Department of Health is a directly relevant contextual authority or primary-source anchor for The rule and journey differ; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: Hawai‘i State Department of Health is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "The rule and journey differ. Compare formal policy with the burden of navigating it.", "The problem: The rule and journey differ fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 048 prototype. Show the interaction or decision path, not an invented result.", "Implication: The rule and journey differ can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 048, The rule and journey differ: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The rule and journey differ. Compare formal policy with the burden of navigating it.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/048/build-048-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 048, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "The rule and journey differ. Compare formal policy with the burden of navigating it.", "The problem: The rule and journey differ fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 048 prototype. Show the interaction or decision path, not an invented result.", "Implication: The rule and journey differ can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 048, The rule and journey differ: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The rule and journey differ fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “The rule and journey differ. Compare formal policy with the burden of navigating it.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 048, 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." }, { "slide": 3, "stage": "System", "copy": [ "The rule and journey differ. Compare formal policy with the burden of navigating it.", "The problem: The rule and journey differ fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 048 prototype. Show the interaction or decision path, not an invented result.", "Implication: The rule and journey differ can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 048, The rule and journey differ: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The rule and journey differ mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 048, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "The rule and journey differ. Compare formal policy with the burden of navigating it.", "The problem: The rule and journey differ fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 048 prototype. Show the interaction or decision path, not an invented result.", "Implication: The rule and journey differ can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 048, The rule and journey differ: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Hawai‘i State Department of Health” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 048, 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://health.hawaii.gov/medicalcannabis/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "The rule and journey differ. Compare formal policy with the burden of navigating it.", "The problem: The rule and journey differ fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 048 prototype. Show the interaction or decision path, not an invented result.", "Implication: The rule and journey differ can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 048, The rule and journey differ: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 048 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 048, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 048, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "The rule and journey differ. Compare formal policy with the burden of navigating it.", "The problem: The rule and journey differ fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 048 prototype. Show the interaction or decision path, not an invented result.", "Implication: The rule and journey differ can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 048, The rule and journey differ: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The rule and journey differ can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 048, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "The rule and journey differ. Compare formal policy with the burden of navigating it.", "The problem: The rule and journey differ fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 048 prototype. Show the interaction or decision path, not an invented result.", "Implication: The rule and journey differ can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 048, The rule and journey differ: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 048, The rule and journey differ: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 048, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 048, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "049", "title": "A preference is not permanent", "template": "RN Builds 4:5 / access-context-and-literacy / Build 049", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/049/build-049-linkedin-poster.png", "altText": "Build 049, A preference is not permanent. Creator-owned 4:5 typographic opening frame. Visible text: “A preference is not permanent. Build private personalization that can change with context.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "privacy framework", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for A preference is not permanent; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A preference is not permanent. Build private personalization that can change with context.", "The problem: A preference is not permanent fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 049 prototype. Show the interaction or decision path, not an invented result.", "Implication: A preference is not permanent can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 049, A preference is not permanent: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A preference is not permanent. Build private personalization that can change with context.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/049/build-049-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 049, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A preference is not permanent. Build private personalization that can change with context.", "The problem: A preference is not permanent fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 049 prototype. Show the interaction or decision path, not an invented result.", "Implication: A preference is not permanent can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 049, A preference is not permanent: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: A preference is not permanent fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A preference is not permanent. Build private personalization that can change with context.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 049, 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." }, { "slide": 3, "stage": "System", "copy": [ "A preference is not permanent. Build private personalization that can change with context.", "The problem: A preference is not permanent fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 049 prototype. Show the interaction or decision path, not an invented result.", "Implication: A preference is not permanent can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 049, A preference is not permanent: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the A preference is not permanent mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 049, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A preference is not permanent. Build private personalization that can change with context.", "The problem: A preference is not permanent fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 049 prototype. Show the interaction or decision path, not an invented result.", "Implication: A preference is not permanent can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 049, A preference is not permanent: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “National Institute of Standards and Technology” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 049, 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://doi.org/10.6028/NIST.CSWP.01162020; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A preference is not permanent. Build private personalization that can change with context.", "The problem: A preference is not permanent fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 049 prototype. Show the interaction or decision path, not an invented result.", "Implication: A preference is not permanent can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 049, A preference is not permanent: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 049 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 049, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 049, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A preference is not permanent. Build private personalization that can change with context.", "The problem: A preference is not permanent fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 049 prototype. Show the interaction or decision path, not an invented result.", "Implication: A preference is not permanent can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 049, A preference is not permanent: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: A preference is not permanent can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 049, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A preference is not permanent. Build private personalization that can change with context.", "The problem: A preference is not permanent fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 049 prototype. Show the interaction or decision path, not an invented result.", "Implication: A preference is not permanent can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 049, A preference is not permanent: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 049, A preference is not permanent: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 049, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 049, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "050", "title": "Environment Assumption & Tradeoff Explorer", "template": "RN Builds 4:5 / access-context-and-literacy / Build 050", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/050/build-050-linkedin-poster.png", "altText": "Build 050, Environment Assumption & Tradeoff Explorer. Creator-owned 4:5 typographic opening frame. Visible text: “A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "CDC / NIOSH", "type": "occupational-health authority", "relevance": "CDC / NIOSH is a directly relevant contextual authority or primary-source anchor for Environment Assumption & Tradeoff Explorer; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: CDC / NIOSH is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.", "The problem: Environment Assumption & Tradeoff Explorer fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC / NIOSH frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 050 prototype. Show the interaction or decision path, not an invented result.", "Implication: Environment Assumption & Tradeoff Explorer can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 050, Environment Assumption & Tradeoff Explorer: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/050/build-050-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 050, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.", "The problem: Environment Assumption & Tradeoff Explorer fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC / NIOSH frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 050 prototype. Show the interaction or decision path, not an invented result.", "Implication: Environment Assumption & Tradeoff Explorer can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 050, Environment Assumption & Tradeoff Explorer: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Environment Assumption & Tradeoff Explorer fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 050, 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." }, { "slide": 3, "stage": "System", "copy": [ "A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.", "The problem: Environment Assumption & Tradeoff Explorer fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC / NIOSH frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 050 prototype. Show the interaction or decision path, not an invented result.", "Implication: Environment Assumption & Tradeoff Explorer can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 050, Environment Assumption & Tradeoff Explorer: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Environment Assumption & Tradeoff Explorer mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 050, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.", "The problem: Environment Assumption & Tradeoff Explorer fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC / NIOSH frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 050 prototype. Show the interaction or decision path, not an invented result.", "Implication: Environment Assumption & Tradeoff Explorer can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 050, Environment Assumption & Tradeoff Explorer: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: CDC / NIOSH frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “CDC / NIOSH” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 050, 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.cdc.gov/niosh/noise/about/index.html; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.", "The problem: Environment Assumption & Tradeoff Explorer fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC / NIOSH frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 050 prototype. Show the interaction or decision path, not an invented result.", "Implication: Environment Assumption & Tradeoff Explorer can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 050, Environment Assumption & Tradeoff Explorer: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 050 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 050, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 050, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.", "The problem: Environment Assumption & Tradeoff Explorer fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC / NIOSH frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 050 prototype. Show the interaction or decision path, not an invented result.", "Implication: Environment Assumption & Tradeoff Explorer can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 050, Environment Assumption & Tradeoff Explorer: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Environment Assumption & Tradeoff Explorer can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 050, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A ROOM MODEL IS NOT EVIDENCE. A fictional room can expose assumptions without claiming how a real person will respond.", "The problem: Environment Assumption & Tradeoff Explorer fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC / NIOSH frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 050 prototype. Show the interaction or decision path, not an invented result.", "Implication: Environment Assumption & Tradeoff Explorer can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 050, Environment Assumption & Tradeoff Explorer: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 050, Environment Assumption & Tradeoff Explorer: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 050, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 050, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "051", "title": "Adaptive Cannabis Source Navigator", "template": "RN Builds 4:5 / access-context-and-literacy / Build 051", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/051/build-051-linkedin-poster.png", "altText": "Build 051, Adaptive Cannabis Source Navigator. Creator-owned 4:5 typographic opening frame. Visible text: “ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health", "type": "health and state regulatory authorities", "relevance": "U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health is a directly relevant contextual authority or primary-source anchor for Adaptive Cannabis Source Navigator; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.", "The problem: Adaptive Cannabis Source Navigator fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 051 prototype. Show the interaction or decision path, not an invented result.", "Implication: Adaptive Cannabis Source Navigator can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 051, Adaptive Cannabis Source Navigator: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/051/build-051-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 051, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.", "The problem: Adaptive Cannabis Source Navigator fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 051 prototype. Show the interaction or decision path, not an invented result.", "Implication: Adaptive Cannabis Source Navigator can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 051, Adaptive Cannabis Source Navigator: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Adaptive Cannabis Source Navigator fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 051, 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." }, { "slide": 3, "stage": "System", "copy": [ "ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.", "The problem: Adaptive Cannabis Source Navigator fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 051 prototype. Show the interaction or decision path, not an invented result.", "Implication: Adaptive Cannabis Source Navigator can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 051, Adaptive Cannabis Source Navigator: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Adaptive Cannabis Source Navigator mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 051, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.", "The problem: Adaptive Cannabis Source Navigator fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 051 prototype. Show the interaction or decision path, not an invented result.", "Implication: Adaptive Cannabis Source Navigator can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 051, Adaptive Cannabis Source Navigator: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 051, 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.fda.gov/consumers/consumer-updates/what-you-need-know-and-what-were-working-find-out-about-products-containing-cannabis-or-cannabis; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.", "The problem: Adaptive Cannabis Source Navigator fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 051 prototype. Show the interaction or decision path, not an invented result.", "Implication: Adaptive Cannabis Source Navigator can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 051, Adaptive Cannabis Source Navigator: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 051 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 051, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 051, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.", "The problem: Adaptive Cannabis Source Navigator fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 051 prototype. Show the interaction or decision path, not an invented result.", "Implication: Adaptive Cannabis Source Navigator can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 051, Adaptive Cannabis Source Navigator: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Adaptive Cannabis Source Navigator can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 051, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "ONE QUESTION DOES NOT NEED EVERY LESSON. A fictional learner’s topic can change source order without creating personal advice.", "The problem: Adaptive Cannabis Source Navigator fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 051 prototype. Show the interaction or decision path, not an invented result.", "Implication: Adaptive Cannabis Source Navigator can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 051, Adaptive Cannabis Source Navigator: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 051, Adaptive Cannabis Source Navigator: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 051, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 051, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "052", "title": "Synthetic Cannabis Comparison Literacy", "template": "RN Builds 4:5 / access-context-and-literacy / Build 052", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/052/build-052-linkedin-poster.png", "altText": "Build 052, Synthetic Cannabis Comparison Literacy. Creator-owned 4:5 typographic opening frame. Visible text: “A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health", "type": "health and product-regulatory authorities", "relevance": "U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health is a directly relevant contextual authority or primary-source anchor for Synthetic Cannabis Comparison Literacy; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.", "The problem: Synthetic Cannabis Comparison Literacy fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 052 prototype. Show the interaction or decision path, not an invented result.", "Implication: Synthetic Cannabis Comparison Literacy can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 052, Synthetic Cannabis Comparison Literacy: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/052/build-052-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 052, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.", "The problem: Synthetic Cannabis Comparison Literacy fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 052 prototype. Show the interaction or decision path, not an invented result.", "Implication: Synthetic Cannabis Comparison Literacy can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 052, Synthetic Cannabis Comparison Literacy: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Synthetic Cannabis Comparison Literacy fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 052, 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." }, { "slide": 3, "stage": "System", "copy": [ "A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.", "The problem: Synthetic Cannabis Comparison Literacy fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 052 prototype. Show the interaction or decision path, not an invented result.", "Implication: Synthetic Cannabis Comparison Literacy can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 052, Synthetic Cannabis Comparison Literacy: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Synthetic Cannabis Comparison Literacy mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 052, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.", "The problem: Synthetic Cannabis Comparison Literacy fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 052 prototype. Show the interaction or decision path, not an invented result.", "Implication: Synthetic Cannabis Comparison Literacy can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 052, Synthetic Cannabis Comparison Literacy: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 052, 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.fda.gov/consumers/consumer-updates/what-you-need-know-and-what-were-working-find-out-about-products-containing-cannabis-or-cannabis; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.", "The problem: Synthetic Cannabis Comparison Literacy fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 052 prototype. Show the interaction or decision path, not an invented result.", "Implication: Synthetic Cannabis Comparison Literacy can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 052, Synthetic Cannabis Comparison Literacy: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 052 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 052, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 052, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.", "The problem: Synthetic Cannabis Comparison Literacy fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 052 prototype. Show the interaction or decision path, not an invented result.", "Implication: Synthetic Cannabis Comparison Literacy can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 052, Synthetic Cannabis Comparison Literacy: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Synthetic Cannabis Comparison Literacy can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 052, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A NAME IS NOT A VERIFIED PRODUCT RECORD. A familiar label does not supply verified identity, composition, quality, effect or safety.", "The problem: Synthetic Cannabis Comparison Literacy fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration + Centers for Disease Control and Prevention + Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 052 prototype. Show the interaction or decision path, not an invented result.", "Implication: Synthetic Cannabis Comparison Literacy can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 052, Synthetic Cannabis Comparison Literacy: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 052, Synthetic Cannabis Comparison Literacy: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 052, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 052, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "053", "title": "Run a Tiny Experiment", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 053", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/053/build-053-linkedin-poster.png", "altText": "Build 053, Run a Tiny Experiment. Creator-owned 4:5 typographic opening frame. Visible text: “ONE DIFFERENT DAY IS NOT AN EXPERIMENT.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. National Library of Medicine", "type": "federal research registry", "relevance": "U.S. National Library of Medicine is a directly relevant contextual authority or primary-source anchor for Run a Tiny Experiment; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: U.S. National Library of Medicine is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "ONE DIFFERENT DAY IS NOT AN EXPERIMENT.", "The problem: Run a Tiny Experiment fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 053 prototype. Show the interaction or decision path, not an invented result.", "Implication: Run a Tiny Experiment can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 053, Run a Tiny Experiment: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "ONE DIFFERENT DAY IS NOT AN EXPERIMENT.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/053/build-053-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 053, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "ONE DIFFERENT DAY IS NOT AN EXPERIMENT.", "The problem: Run a Tiny Experiment fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 053 prototype. Show the interaction or decision path, not an invented result.", "Implication: Run a Tiny Experiment can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 053, Run a Tiny Experiment: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Run a Tiny Experiment fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “ONE DIFFERENT DAY IS NOT AN EXPERIMENT.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 053, 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." }, { "slide": 3, "stage": "System", "copy": [ "ONE DIFFERENT DAY IS NOT AN EXPERIMENT.", "The problem: Run a Tiny Experiment fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 053 prototype. Show the interaction or decision path, not an invented result.", "Implication: Run a Tiny Experiment can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 053, Run a Tiny Experiment: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Run a Tiny Experiment mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 053, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "ONE DIFFERENT DAY IS NOT AN EXPERIMENT.", "The problem: Run a Tiny Experiment fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 053 prototype. Show the interaction or decision path, not an invented result.", "Implication: Run a Tiny Experiment can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 053, Run a Tiny Experiment: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. National Library of Medicine” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 053, 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://clinicaltrials.gov/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "ONE DIFFERENT DAY IS NOT AN EXPERIMENT.", "The problem: Run a Tiny Experiment fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 053 prototype. Show the interaction or decision path, not an invented result.", "Implication: Run a Tiny Experiment can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 053, Run a Tiny Experiment: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 053 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 053, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 053, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "ONE DIFFERENT DAY IS NOT AN EXPERIMENT.", "The problem: Run a Tiny Experiment fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 053 prototype. Show the interaction or decision path, not an invented result.", "Implication: Run a Tiny Experiment can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 053, Run a Tiny Experiment: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Run a Tiny Experiment can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 053, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "ONE DIFFERENT DAY IS NOT AN EXPERIMENT.", "The problem: Run a Tiny Experiment fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 053 prototype. Show the interaction or decision path, not an invented result.", "Implication: Run a Tiny Experiment can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 053, Run a Tiny Experiment: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 053, Run a Tiny Experiment: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 053, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 053, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "054", "title": "Make the Space Adapt to the Person", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 054", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/054/build-054-linkedin-poster.png", "altText": "Build 054, Make the Space Adapt to the Person. Creator-owned 4:5 typographic opening frame. Visible text: “A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "privacy framework", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for Make the Space Adapt to the Person; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.", "The problem: Make the Space Adapt to the Person fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 054 prototype. Show the interaction or decision path, not an invented result.", "Implication: Make the Space Adapt to the Person can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 054, Make the Space Adapt to the Person: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/054/build-054-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 054, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.", "The problem: Make the Space Adapt to the Person fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 054 prototype. Show the interaction or decision path, not an invented result.", "Implication: Make the Space Adapt to the Person can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 054, Make the Space Adapt to the Person: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Make the Space Adapt to the Person fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 054, 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." }, { "slide": 3, "stage": "System", "copy": [ "A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.", "The problem: Make the Space Adapt to the Person fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 054 prototype. Show the interaction or decision path, not an invented result.", "Implication: Make the Space Adapt to the Person can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 054, Make the Space Adapt to the Person: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Make the Space Adapt to the Person mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 054, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.", "The problem: Make the Space Adapt to the Person fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 054 prototype. Show the interaction or decision path, not an invented result.", "Implication: Make the Space Adapt to the Person can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 054, Make the Space Adapt to the Person: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “National Institute of Standards and Technology” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 054, 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://doi.org/10.6028/NIST.CSWP.01162020; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.", "The problem: Make the Space Adapt to the Person fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 054 prototype. Show the interaction or decision path, not an invented result.", "Implication: Make the Space Adapt to the Person can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 054, Make the Space Adapt to the Person: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 054 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 054, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 054, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.", "The problem: Make the Space Adapt to the Person fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 054 prototype. Show the interaction or decision path, not an invented result.", "Implication: Make the Space Adapt to the Person can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 054, Make the Space Adapt to the Person: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Make the Space Adapt to the Person can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 054, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A ROOM CAN ADAPT WITHOUT DECIDING FOR A PERSON.", "The problem: Make the Space Adapt to the Person fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 054 prototype. Show the interaction or decision path, not an invented result.", "Implication: Make the Space Adapt to the Person can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 054, Make the Space Adapt to the Person: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 054, Make the Space Adapt to the Person: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 054, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 054, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "055", "title": "Let the Smart Home Explain Itself", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 055", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/055/build-055-linkedin-poster.png", "altText": "Build 055, Let the Smart Home Explain Itself. Creator-owned 4:5 typographic opening frame. Visible text: “A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "cybersecurity standard", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for Let the Smart Home Explain Itself; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.", "The problem: Let the Smart Home Explain Itself fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 055 prototype. Show the interaction or decision path, not an invented result.", "Implication: Let the Smart Home Explain Itself can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 055, Let the Smart Home Explain Itself: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/055/build-055-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 055, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.", "The problem: Let the Smart Home Explain Itself fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 055 prototype. Show the interaction or decision path, not an invented result.", "Implication: Let the Smart Home Explain Itself can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 055, Let the Smart Home Explain Itself: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Let the Smart Home Explain Itself fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 055, 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." }, { "slide": 3, "stage": "System", "copy": [ "A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.", "The problem: Let the Smart Home Explain Itself fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 055 prototype. Show the interaction or decision path, not an invented result.", "Implication: Let the Smart Home Explain Itself can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 055, Let the Smart Home Explain Itself: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Let the Smart Home Explain Itself mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 055, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.", "The problem: Let the Smart Home Explain Itself fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 055 prototype. Show the interaction or decision path, not an invented result.", "Implication: Let the Smart Home Explain Itself can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 055, Let the Smart Home Explain Itself: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “National Institute of Standards and Technology” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 055, 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://doi.org/10.6028/NIST.IR.8259A; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.", "The problem: Let the Smart Home Explain Itself fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 055 prototype. Show the interaction or decision path, not an invented result.", "Implication: Let the Smart Home Explain Itself can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 055, Let the Smart Home Explain Itself: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 055 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 055, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 055, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.", "The problem: Let the Smart Home Explain Itself fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 055 prototype. Show the interaction or decision path, not an invented result.", "Implication: Let the Smart Home Explain Itself can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 055, Let the Smart Home Explain Itself: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Let the Smart Home Explain Itself can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 055, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A SMART HOME ACTION NEEDS AN ACCOUNTABLE STORY.", "The problem: Let the Smart Home Explain Itself fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 055 prototype. Show the interaction or decision path, not an invented result.", "Implication: Let the Smart Home Explain Itself can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 055, Let the Smart Home Explain Itself: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 055, Let the Smart Home Explain Itself: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 055, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 055, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "056", "title": "What Do You Actually Own?", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 056", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/056/build-056-linkedin-poster.png", "altText": "Build 056, What Do You Actually Own? Creator-owned 4:5 typographic opening frame. Visible text: “A LIST OF ASSETS IS NOT A MOAT.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. Patent and Trademark Office + U.S. Copyright Office", "type": "federal intellectual-property authorities", "relevance": "U.S. Patent and Trademark Office + U.S. Copyright Office is a directly relevant contextual authority or primary-source anchor for What Do You Actually Own?; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: U.S. Patent and Trademark Office + U.S. Copyright Office is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A LIST OF ASSETS IS NOT A MOAT.", "The problem: What Do You Actually Own? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 056 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Do You Actually Own? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 056, What Do You Actually Own?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A LIST OF ASSETS IS NOT A MOAT.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/056/build-056-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 056, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A LIST OF ASSETS IS NOT A MOAT.", "The problem: What Do You Actually Own? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 056 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Do You Actually Own? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 056, What Do You Actually Own?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: What Do You Actually Own? fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A LIST OF ASSETS IS NOT A MOAT.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 056, 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." }, { "slide": 3, "stage": "System", "copy": [ "A LIST OF ASSETS IS NOT A MOAT.", "The problem: What Do You Actually Own? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 056 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Do You Actually Own? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 056, What Do You Actually Own?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the What Do You Actually Own? mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 056, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A LIST OF ASSETS IS NOT A MOAT.", "The problem: What Do You Actually Own? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 056 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Do You Actually Own? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 056, What Do You Actually Own?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. Patent and Trademark Office + U.S. Copyright Office” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 056, 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.uspto.gov/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A LIST OF ASSETS IS NOT A MOAT.", "The problem: What Do You Actually Own? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 056 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Do You Actually Own? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 056, What Do You Actually Own?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 056 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 056, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 056, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A LIST OF ASSETS IS NOT A MOAT.", "The problem: What Do You Actually Own? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 056 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Do You Actually Own? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 056, What Do You Actually Own?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: What Do You Actually Own? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 056, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A LIST OF ASSETS IS NOT A MOAT.", "The problem: What Do You Actually Own? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 056 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Do You Actually Own? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 056, What Do You Actually Own?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 056, What Do You Actually Own?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 056, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 056, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "057", "title": "Show Me Where This Content Came From", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 057", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/source-excerpts/build-057-source-excerpt-hold.svg", "altText": "Sequential text composite from PROV-O Starting Point Terms: the introductory provenance-description passage, then separately labeled Entity and Activity definitions.", "credit": "Copyright © 2013 W3C®. Excerpt subject to the W3C document-use rules linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231", "sourceUrl": "https://www.w3.org/TR/2013/REC-prov-o-20130430/", "rollbackAssetUrl": "/media/builds/057/build-057-linkedin-poster.png" }, "recognizableEntity": { "label": "W3C", "type": "provenance standard", "relevance": "W3C is a directly relevant contextual authority or primary-source anchor for Show Me Where This Content Came From; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: W3C is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A FINISHED FILE HIDES ITS PRODUCTION HISTORY.", "The problem: Show Me Where This Content Came From fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 057 prototype. Show the interaction or decision path, not an invented result.", "Implication: Show Me Where This Content Came From can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 057, Show Me Where This Content Came From: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A FINISHED FILE HIDES ITS PRODUCTION HISTORY.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/source-excerpts/build-057-source-excerpt-hold.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 1 alt text must identify Build 057, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2013 W3C®. W3C document-use rules linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231" }, { "slide": 2, "stage": "Problem", "copy": [ "A FINISHED FILE HIDES ITS PRODUCTION HISTORY.", "The problem: Show Me Where This Content Came From fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 057 prototype. Show the interaction or decision path, not an invented result.", "Implication: Show Me Where This Content Came From can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 057, Show Me Where This Content Came From: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Show Me Where This Content Came From fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A FINISHED FILE HIDES ITS PRODUCTION HISTORY.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 057, 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." }, { "slide": 3, "stage": "System", "copy": [ "A FINISHED FILE HIDES ITS PRODUCTION HISTORY.", "The problem: Show Me Where This Content Came From fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 057 prototype. Show the interaction or decision path, not an invented result.", "Implication: Show Me Where This Content Came From can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 057, Show Me Where This Content Came From: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Show Me Where This Content Came From mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 057, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A FINISHED FILE HIDES ITS PRODUCTION HISTORY.", "The problem: Show Me Where This Content Came From fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 057 prototype. Show the interaction or decision path, not an invented result.", "Implication: Show Me Where This Content Came From can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 057, Show Me Where This Content Came From: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.w3.org/TR/2013/REC-prov-o-20130430/; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 057, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2013 W3C®. Excerpt subject to the W3C document-use rules linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231 Copyright © 2013 W3C®. W3C document-use rules linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231" }, { "slide": 5, "stage": "Demo", "copy": [ "A FINISHED FILE HIDES ITS PRODUCTION HISTORY.", "The problem: Show Me Where This Content Came From fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 057 prototype. Show the interaction or decision path, not an invented result.", "Implication: Show Me Where This Content Came From can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 057, Show Me Where This Content Came From: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 057 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 057, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 057, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A FINISHED FILE HIDES ITS PRODUCTION HISTORY.", "The problem: Show Me Where This Content Came From fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 057 prototype. Show the interaction or decision path, not an invented result.", "Implication: Show Me Where This Content Came From can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 057, Show Me Where This Content Came From: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Show Me Where This Content Came From can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 057, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A FINISHED FILE HIDES ITS PRODUCTION HISTORY.", "The problem: Show Me Where This Content Came From fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 057 prototype. Show the interaction or decision path, not an invented result.", "Implication: Show Me Where This Content Came From can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 057, Show Me Where This Content Came From: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 057, Show Me Where This Content Came From: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 057, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 057, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "058", "title": "Trace a Claim All the Way Back", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 058", "status": "LIVE_OFFICIAL_SOURCE_CONTEXT", "coverMapping": { "assetUrl": "/media/100-builds/source-excerpts/build-058-source-excerpt-hold.svg", "altText": "Sequential text composite from PROV-O Starting Point Terms containing an Entity definition and separately labeled generation and derivation relation passages.", "credit": "Copyright © 2013 W3C®. Excerpt subject to the W3C document-use rules linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231", "sourceUrl": "https://www.w3.org/TR/2013/REC-prov-o-20130430/", "rollbackAssetUrl": "/media/builds/058/build-058-linkedin-poster.png" }, "recognizableEntity": { "label": "W3C", "type": "provenance standard", "relevance": "W3C is a directly relevant contextual authority or primary-source anchor for Trace a Claim All the Way Back; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: W3C is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A CITATION CAN HIDE A BROKEN SUPPORT PATH.", "The problem: Trace a Claim All the Way Back fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 058 prototype. Show the interaction or decision path, not an invented result.", "Implication: Trace a Claim All the Way Back can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 058, Trace a Claim All the Way Back: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A CITATION CAN HIDE A BROKEN SUPPORT PATH.", "visualGuidance": "Use the complete live official source-context cover at /media/100-builds/source-excerpts/build-058-source-excerpt-hold.svg. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 1 alt text must identify Build 058, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2013 W3C®. W3C document-use rules linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231" }, { "slide": 2, "stage": "Problem", "copy": [ "A CITATION CAN HIDE A BROKEN SUPPORT PATH.", "The problem: Trace a Claim All the Way Back fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 058 prototype. Show the interaction or decision path, not an invented result.", "Implication: Trace a Claim All the Way Back can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 058, Trace a Claim All the Way Back: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Trace a Claim All the Way Back fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A CITATION CAN HIDE A BROKEN SUPPORT PATH.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 058, 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." }, { "slide": 3, "stage": "System", "copy": [ "A CITATION CAN HIDE A BROKEN SUPPORT PATH.", "The problem: Trace a Claim All the Way Back fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 058 prototype. Show the interaction or decision path, not an invented result.", "Implication: Trace a Claim All the Way Back can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 058, Trace a Claim All the Way Back: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Trace a Claim All the Way Back mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 058, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A CITATION CAN HIDE A BROKEN SUPPORT PATH.", "The problem: Trace a Claim All the Way Back fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 058 prototype. Show the interaction or decision path, not an invented result.", "Implication: Trace a Claim All the Way Back can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 058, Trace a Claim All the Way Back: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "visualGuidance": "Use only the recorded official source-context treatment from https://www.w3.org/TR/2013/REC-prov-o-20130430/; preserve attribution, rights line, no-endorsement language, and exact claim boundary.", "claimBoundary": "APPROVED SOURCE-CONTEXT EXCERPT; not evidence of build performance, compliance, completeness, safety, truth, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 058, the evidence function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Copyright © 2013 W3C®. Excerpt subject to the W3C document-use rules linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231 Copyright © 2013 W3C®. W3C document-use rules linked by the immutable Recommendation: https://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231" }, { "slide": 5, "stage": "Demo", "copy": [ "A CITATION CAN HIDE A BROKEN SUPPORT PATH.", "The problem: Trace a Claim All the Way Back fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 058 prototype. Show the interaction or decision path, not an invented result.", "Implication: Trace a Claim All the Way Back can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 058, Trace a Claim All the Way Back: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 058 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 058, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 058, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A CITATION CAN HIDE A BROKEN SUPPORT PATH.", "The problem: Trace a Claim All the Way Back fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 058 prototype. Show the interaction or decision path, not an invented result.", "Implication: Trace a Claim All the Way Back can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 058, Trace a Claim All the Way Back: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Trace a Claim All the Way Back can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 058, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A CITATION CAN HIDE A BROKEN SUPPORT PATH.", "The problem: Trace a Claim All the Way Back fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence context: W3C PROV-O Recommendation. Sequential context excerpt; any composite or contextual limit is visibly labeled. No affiliation or endorsement.", "Demo: walk through one bounded state change in the Build 058 prototype. Show the interaction or decision path, not an invented result.", "Implication: Trace a Claim All the Way Back can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 058, Trace a Claim All the Way Back: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 058, Trace a Claim All the Way Back: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 058, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 058, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "059", "title": "Verify the Legal Citation", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 059", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/059/build-059-linkedin-poster.png", "altText": "Build 059, Verify the Legal Citation. Creator-owned 4:5 typographic opening frame. Visible text: “A CONVINCING LEGAL CITATION CAN STILL FAIL.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Supreme Court of the United States + Library of Congress", "type": "primary legal authorities", "relevance": "Supreme Court of the United States + Library of Congress is a directly relevant contextual authority or primary-source anchor for Verify the Legal Citation; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: Supreme Court of the United States + Library of Congress is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A CONVINCING LEGAL CITATION CAN STILL FAIL.", "The problem: Verify the Legal Citation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supreme Court of the United States + Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 059 prototype. Show the interaction or decision path, not an invented result.", "Implication: Verify the Legal Citation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 059, Verify the Legal Citation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A CONVINCING LEGAL CITATION CAN STILL FAIL.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/059/build-059-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 059, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A CONVINCING LEGAL CITATION CAN STILL FAIL.", "The problem: Verify the Legal Citation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supreme Court of the United States + Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 059 prototype. Show the interaction or decision path, not an invented result.", "Implication: Verify the Legal Citation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 059, Verify the Legal Citation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Verify the Legal Citation fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A CONVINCING LEGAL CITATION CAN STILL FAIL.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 059, 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." }, { "slide": 3, "stage": "System", "copy": [ "A CONVINCING LEGAL CITATION CAN STILL FAIL.", "The problem: Verify the Legal Citation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supreme Court of the United States + Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 059 prototype. Show the interaction or decision path, not an invented result.", "Implication: Verify the Legal Citation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 059, Verify the Legal Citation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Verify the Legal Citation mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 059, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A CONVINCING LEGAL CITATION CAN STILL FAIL.", "The problem: Verify the Legal Citation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supreme Court of the United States + Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 059 prototype. Show the interaction or decision path, not an invented result.", "Implication: Verify the Legal Citation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 059, Verify the Legal Citation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Supreme Court of the United States + Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Supreme Court of the United States + Library of Congress” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 059, 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.supremecourt.gov/opinions/opinions.aspx; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A CONVINCING LEGAL CITATION CAN STILL FAIL.", "The problem: Verify the Legal Citation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supreme Court of the United States + Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 059 prototype. Show the interaction or decision path, not an invented result.", "Implication: Verify the Legal Citation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 059, Verify the Legal Citation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 059 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 059, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 059, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A CONVINCING LEGAL CITATION CAN STILL FAIL.", "The problem: Verify the Legal Citation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supreme Court of the United States + Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 059 prototype. Show the interaction or decision path, not an invented result.", "Implication: Verify the Legal Citation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 059, Verify the Legal Citation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Verify the Legal Citation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 059, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A CONVINCING LEGAL CITATION CAN STILL FAIL.", "The problem: Verify the Legal Citation fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supreme Court of the United States + Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 059 prototype. Show the interaction or decision path, not an invented result.", "Implication: Verify the Legal Citation can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 059, Verify the Legal Citation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 059, Verify the Legal Citation: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 059, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 059, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "060", "title": "Catch the IP Before It Disappears", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 060", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/060/build-060-linkedin-poster.png", "altText": "Build 060, Catch the IP Before It Disappears. Creator-owned 4:5 typographic opening frame. Visible text: “VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. Patent and Trademark Office + U.S. Copyright Office", "type": "federal intellectual-property authorities", "relevance": "U.S. Patent and Trademark Office + U.S. Copyright Office is a directly relevant contextual authority or primary-source anchor for Catch the IP Before It Disappears; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: U.S. Patent and Trademark Office + U.S. Copyright Office is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.", "The problem: Catch the IP Before It Disappears fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 060 prototype. Show the interaction or decision path, not an invented result.", "Implication: Catch the IP Before It Disappears can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 060, Catch the IP Before It Disappears: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/060/build-060-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 060, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.", "The problem: Catch the IP Before It Disappears fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 060 prototype. Show the interaction or decision path, not an invented result.", "Implication: Catch the IP Before It Disappears can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 060, Catch the IP Before It Disappears: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Catch the IP Before It Disappears fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 060, 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." }, { "slide": 3, "stage": "System", "copy": [ "VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.", "The problem: Catch the IP Before It Disappears fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 060 prototype. Show the interaction or decision path, not an invented result.", "Implication: Catch the IP Before It Disappears can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 060, Catch the IP Before It Disappears: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Catch the IP Before It Disappears mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 060, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.", "The problem: Catch the IP Before It Disappears fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 060 prototype. Show the interaction or decision path, not an invented result.", "Implication: Catch the IP Before It Disappears can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 060, Catch the IP Before It Disappears: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. Patent and Trademark Office + U.S. Copyright Office” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 060, 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.uspto.gov/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.", "The problem: Catch the IP Before It Disappears fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 060 prototype. Show the interaction or decision path, not an invented result.", "Implication: Catch the IP Before It Disappears can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 060, Catch the IP Before It Disappears: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 060 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 060, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 060, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.", "The problem: Catch the IP Before It Disappears fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 060 prototype. Show the interaction or decision path, not an invented result.", "Implication: Catch the IP Before It Disappears can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 060, Catch the IP Before It Disappears: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Catch the IP Before It Disappears can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 060, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "VALUABLE WORK CAN DISAPPEAR INTO THE WORKDAY.", "The problem: Catch the IP Before It Disappears fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Patent and Trademark Office + U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 060 prototype. Show the interaction or decision path, not an invented result.", "Implication: Catch the IP Before It Disappears can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 060, Catch the IP Before It Disappears: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 060, Catch the IP Before It Disappears: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 060, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 060, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "061", "title": "Why Did We Decide That?", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 061", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/061/build-061-linkedin-poster.png", "altText": "Build 061, Why Did We Decide That? Creator-owned 4:5 typographic opening frame. Visible text: “A DECISION RECORD CAN LOSE ITS REASONS.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. National Archives and Records Administration", "type": "federal records authority", "relevance": "U.S. National Archives and Records Administration is a directly relevant contextual authority or primary-source anchor for Why Did We Decide That?; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: U.S. National Archives and Records Administration is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A DECISION RECORD CAN LOSE ITS REASONS.", "The problem: Why Did We Decide That? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Archives and Records Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 061 prototype. Show the interaction or decision path, not an invented result.", "Implication: Why Did We Decide That? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 061, Why Did We Decide That?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A DECISION RECORD CAN LOSE ITS REASONS.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/061/build-061-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 061, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A DECISION RECORD CAN LOSE ITS REASONS.", "The problem: Why Did We Decide That? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Archives and Records Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 061 prototype. Show the interaction or decision path, not an invented result.", "Implication: Why Did We Decide That? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 061, Why Did We Decide That?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Why Did We Decide That? fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A DECISION RECORD CAN LOSE ITS REASONS.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 061, 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." }, { "slide": 3, "stage": "System", "copy": [ "A DECISION RECORD CAN LOSE ITS REASONS.", "The problem: Why Did We Decide That? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Archives and Records Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 061 prototype. Show the interaction or decision path, not an invented result.", "Implication: Why Did We Decide That? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 061, Why Did We Decide That?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Why Did We Decide That? mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 061, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A DECISION RECORD CAN LOSE ITS REASONS.", "The problem: Why Did We Decide That? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Archives and Records Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 061 prototype. Show the interaction or decision path, not an invented result.", "Implication: Why Did We Decide That? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 061, Why Did We Decide That?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: U.S. National Archives and Records Administration frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. National Archives and Records Administration” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 061, 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.archives.gov/records-mgmt; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A DECISION RECORD CAN LOSE ITS REASONS.", "The problem: Why Did We Decide That? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Archives and Records Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 061 prototype. Show the interaction or decision path, not an invented result.", "Implication: Why Did We Decide That? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 061, Why Did We Decide That?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 061 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 061, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 061, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A DECISION RECORD CAN LOSE ITS REASONS.", "The problem: Why Did We Decide That? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Archives and Records Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 061 prototype. Show the interaction or decision path, not an invented result.", "Implication: Why Did We Decide That? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 061, Why Did We Decide That?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Why Did We Decide That? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 061, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A DECISION RECORD CAN LOSE ITS REASONS.", "The problem: Why Did We Decide That? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Archives and Records Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 061 prototype. Show the interaction or decision path, not an invented result.", "Implication: Why Did We Decide That? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 061, Why Did We Decide That?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 061, Why Did We Decide That?: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 061, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 061, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "062", "title": "The Interview Is More Than a Transcript", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 062", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/062/build-062-linkedin-poster.png", "altText": "Build 062, The Interview Is More Than a Transcript. Creator-owned 4:5 typographic opening frame. Visible text: “A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Library of Congress", "type": "primary-source oral-history repository", "relevance": "Library of Congress is a directly relevant contextual authority or primary-source anchor for The Interview Is More Than a Transcript; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: Library of Congress is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.", "The problem: The Interview Is More Than a Transcript fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 062 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Interview Is More Than a Transcript can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 062, The Interview Is More Than a Transcript: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/062/build-062-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 062, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.", "The problem: The Interview Is More Than a Transcript fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 062 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Interview Is More Than a Transcript can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 062, The Interview Is More Than a Transcript: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The Interview Is More Than a Transcript fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 062, 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." }, { "slide": 3, "stage": "System", "copy": [ "A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.", "The problem: The Interview Is More Than a Transcript fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 062 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Interview Is More Than a Transcript can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 062, The Interview Is More Than a Transcript: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Interview Is More Than a Transcript mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 062, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.", "The problem: The Interview Is More Than a Transcript fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 062 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Interview Is More Than a Transcript can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 062, The Interview Is More Than a Transcript: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Library of Congress” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 062, 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.loc.gov/collections/veterans-history-project-collection/about-this-collection/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.", "The problem: The Interview Is More Than a Transcript fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 062 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Interview Is More Than a Transcript can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 062, The Interview Is More Than a Transcript: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 062 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 062, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 062, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.", "The problem: The Interview Is More Than a Transcript fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 062 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Interview Is More Than a Transcript can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 062, The Interview Is More Than a Transcript: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The Interview Is More Than a Transcript can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 062, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A TRANSCRIPT IS NOT THE WHOLE INTERVIEW.", "The problem: The Interview Is More Than a Transcript fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Library of Congress frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 062 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Interview Is More Than a Transcript can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 062, The Interview Is More Than a Transcript: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 062, The Interview Is More Than a Transcript: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 062, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 062, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "063", "title": "Research That Does Not Die in a Folder", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 063", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/063/build-063-linkedin-poster.png", "altText": "Build 063, Research That Does Not Die in a Folder. Creator-owned 4:5 typographic opening frame. Visible text: “RESEARCH THAT DOES NOT DIE IN A FOLDER.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. National Library of Medicine", "type": "biomedical literature index", "relevance": "U.S. National Library of Medicine is a directly relevant contextual authority or primary-source anchor for Research That Does Not Die in a Folder; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: U.S. National Library of Medicine is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "RESEARCH THAT DOES NOT DIE IN A FOLDER.", "The problem: Research That Does Not Die in a Folder fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 063 prototype. Show the interaction or decision path, not an invented result.", "Implication: Research That Does Not Die in a Folder can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 063, Research That Does Not Die in a Folder: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "RESEARCH THAT DOES NOT DIE IN A FOLDER.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/063/build-063-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 063, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "RESEARCH THAT DOES NOT DIE IN A FOLDER.", "The problem: Research That Does Not Die in a Folder fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 063 prototype. Show the interaction or decision path, not an invented result.", "Implication: Research That Does Not Die in a Folder can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 063, Research That Does Not Die in a Folder: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Research That Does Not Die in a Folder fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “RESEARCH THAT DOES NOT DIE IN A FOLDER.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 063, 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." }, { "slide": 3, "stage": "System", "copy": [ "RESEARCH THAT DOES NOT DIE IN A FOLDER.", "The problem: Research That Does Not Die in a Folder fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 063 prototype. Show the interaction or decision path, not an invented result.", "Implication: Research That Does Not Die in a Folder can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 063, Research That Does Not Die in a Folder: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Research That Does Not Die in a Folder mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 063, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "RESEARCH THAT DOES NOT DIE IN A FOLDER.", "The problem: Research That Does Not Die in a Folder fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 063 prototype. Show the interaction or decision path, not an invented result.", "Implication: Research That Does Not Die in a Folder can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 063, Research That Does Not Die in a Folder: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. National Library of Medicine” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 063, 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://pubmed.ncbi.nlm.nih.gov/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "RESEARCH THAT DOES NOT DIE IN A FOLDER.", "The problem: Research That Does Not Die in a Folder fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 063 prototype. Show the interaction or decision path, not an invented result.", "Implication: Research That Does Not Die in a Folder can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 063, Research That Does Not Die in a Folder: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 063 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 063, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 063, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "RESEARCH THAT DOES NOT DIE IN A FOLDER.", "The problem: Research That Does Not Die in a Folder fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 063 prototype. Show the interaction or decision path, not an invented result.", "Implication: Research That Does Not Die in a Folder can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 063, Research That Does Not Die in a Folder: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Research That Does Not Die in a Folder can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 063, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "RESEARCH THAT DOES NOT DIE IN A FOLDER.", "The problem: Research That Does Not Die in a Folder fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. National Library of Medicine frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 063 prototype. Show the interaction or decision path, not an invented result.", "Implication: Research That Does Not Die in a Folder can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 063, Research That Does Not Die in a Folder: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 063, Research That Does Not Die in a Folder: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 063, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 063, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "064", "title": "An Industry With Amnesia", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 064", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/064/build-064-linkedin-poster.png", "altText": "Build 064, An Industry With Amnesia. Creator-owned 4:5 typographic opening frame. Visible text: “WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Hawai‘i State Department of Health", "type": "state public-health program", "relevance": "Hawai‘i State Department of Health is a directly relevant contextual authority or primary-source anchor for An Industry With Amnesia; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: Hawai‘i State Department of Health is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?", "The problem: An Industry With Amnesia fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 064 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Industry With Amnesia can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 064, An Industry With Amnesia: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?", "visualGuidance": "Use the complete RN-owned cover at /media/builds/064/build-064-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 064, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?", "The problem: An Industry With Amnesia fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 064 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Industry With Amnesia can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 064, An Industry With Amnesia: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: An Industry With Amnesia fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 064, 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." }, { "slide": 3, "stage": "System", "copy": [ "WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?", "The problem: An Industry With Amnesia fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 064 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Industry With Amnesia can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 064, An Industry With Amnesia: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the An Industry With Amnesia mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 064, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?", "The problem: An Industry With Amnesia fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 064 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Industry With Amnesia can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 064, An Industry With Amnesia: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Hawai‘i State Department of Health” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 064, 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://health.hawaii.gov/medicalcannabis/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?", "The problem: An Industry With Amnesia fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 064 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Industry With Amnesia can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 064, An Industry With Amnesia: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 064 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 064, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 064, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?", "The problem: An Industry With Amnesia fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 064 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Industry With Amnesia can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 064, An Industry With Amnesia: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: An Industry With Amnesia can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 064, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "WHEN PEOPLE LEAVE, WHAT DOES THE INSTITUTION REMEMBER?", "The problem: An Industry With Amnesia fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Hawai‘i State Department of Health frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 064 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Industry With Amnesia can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 064, An Industry With Amnesia: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 064, An Industry With Amnesia: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 064, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 064, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "065", "title": "Fictional Psychedelic Pathway Record", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 065", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/065/build-065-linkedin-poster.png", "altText": "Build 065, Fictional Psychedelic Pathway Record. Creator-owned 4:5 typographic opening frame. Visible text: “ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. Food and Drug Administration", "type": "federal clinical-investigation guidance", "relevance": "U.S. Food and Drug Administration is a directly relevant contextual authority or primary-source anchor for Fictional Psychedelic Pathway Record; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: U.S. Food and Drug Administration is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.", "The problem: Fictional Psychedelic Pathway Record fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 065 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Psychedelic Pathway Record can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 065, Fictional Psychedelic Pathway Record: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/065/build-065-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 065, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.", "The problem: Fictional Psychedelic Pathway Record fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 065 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Psychedelic Pathway Record can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 065, Fictional Psychedelic Pathway Record: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: Fictional Psychedelic Pathway Record fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 065, 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." }, { "slide": 3, "stage": "System", "copy": [ "ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.", "The problem: Fictional Psychedelic Pathway Record fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 065 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Psychedelic Pathway Record can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 065, Fictional Psychedelic Pathway Record: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Fictional Psychedelic Pathway Record mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 065, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.", "The problem: Fictional Psychedelic Pathway Record fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 065 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Psychedelic Pathway Record can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 065, Fictional Psychedelic Pathway Record: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: U.S. Food and Drug Administration frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. Food and Drug Administration” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 065, 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.fda.gov/regulatory-information/search-fda-guidance-documents/psychedelic-drugs-considerations-clinical-investigations; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.", "The problem: Fictional Psychedelic Pathway Record fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 065 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Psychedelic Pathway Record can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 065, Fictional Psychedelic Pathway Record: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 065 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 065, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 065, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.", "The problem: Fictional Psychedelic Pathway Record fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 065 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Psychedelic Pathway Record can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 065, Fictional Psychedelic Pathway Record: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: Fictional Psychedelic Pathway Record can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 065, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "ONE EVENT DOES NOT SHOW THE WHOLE RECORD. A fictional session can sit inside a longer modeled pathway without defining care.", "The problem: Fictional Psychedelic Pathway Record fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Food and Drug Administration frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 065 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Psychedelic Pathway Record can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 065, Fictional Psychedelic Pathway Record: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 065, Fictional Psychedelic Pathway Record: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 065, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 065, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "066", "title": "The Firm Knows More Than Its Folders", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 066", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/066/build-066-linkedin-poster.png", "altText": "Build 066, The Firm Knows More Than Its Folders. Creator-owned 4:5 typographic opening frame. Visible text: “THE FIRM KNOWS MORE THAN ITS FOLDERS.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "American Bar Association", "type": "professional-responsibility standards body", "relevance": "American Bar Association is a directly relevant contextual authority or primary-source anchor for The Firm Knows More Than Its Folders; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: American Bar Association is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "THE FIRM KNOWS MORE THAN ITS FOLDERS.", "The problem: The Firm Knows More Than Its Folders fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: American Bar Association frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 066 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Firm Knows More Than Its Folders can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 066, The Firm Knows More Than Its Folders: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "THE FIRM KNOWS MORE THAN ITS FOLDERS.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/066/build-066-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 066, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "THE FIRM KNOWS MORE THAN ITS FOLDERS.", "The problem: The Firm Knows More Than Its Folders fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: American Bar Association frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 066 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Firm Knows More Than Its Folders can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 066, The Firm Knows More Than Its Folders: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: The Firm Knows More Than Its Folders fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “THE FIRM KNOWS MORE THAN ITS FOLDERS.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 066, 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." }, { "slide": 3, "stage": "System", "copy": [ "THE FIRM KNOWS MORE THAN ITS FOLDERS.", "The problem: The Firm Knows More Than Its Folders fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: American Bar Association frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 066 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Firm Knows More Than Its Folders can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 066, The Firm Knows More Than Its Folders: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Firm Knows More Than Its Folders mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 066, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "THE FIRM KNOWS MORE THAN ITS FOLDERS.", "The problem: The Firm Knows More Than Its Folders fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: American Bar Association frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 066 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Firm Knows More Than Its Folders can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 066, The Firm Knows More Than Its Folders: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: American Bar Association frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “American Bar Association” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 066, 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.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "THE FIRM KNOWS MORE THAN ITS FOLDERS.", "The problem: The Firm Knows More Than Its Folders fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: American Bar Association frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 066 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Firm Knows More Than Its Folders can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 066, The Firm Knows More Than Its Folders: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 066 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 066, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 066, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "THE FIRM KNOWS MORE THAN ITS FOLDERS.", "The problem: The Firm Knows More Than Its Folders fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: American Bar Association frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 066 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Firm Knows More Than Its Folders can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 066, The Firm Knows More Than Its Folders: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: The Firm Knows More Than Its Folders can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 066, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "THE FIRM KNOWS MORE THAN ITS FOLDERS.", "The problem: The Firm Knows More Than Its Folders fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: American Bar Association frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 066 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Firm Knows More Than Its Folders can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 066, The Firm Knows More Than Its Folders: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 066, The Firm Knows More Than Its Folders: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 066, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 066, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "067", "title": "A Digital Twin Begins With Gaps", "template": "RN Builds 4:5 / evidence-IP-and-institutional-memory / Build 067", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/067/build-067-linkedin-poster.png", "altText": "Build 067, A Digital Twin Begins With Gaps. Creator-owned 4:5 typographic opening frame. Visible text: “A DIGITAL TWIN BEGINS WITH GAPS.”", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "National Institute of Standards and Technology", "type": "privacy framework", "relevance": "National Institute of Standards and Technology is a directly relevant contextual authority or primary-source anchor for A Digital Twin Begins With Gaps; it is selected for domain relevance, not fame. It is not the cover subject and does not endorse RN or the build.", "authorizationBoundary": "Context only: National Institute of Standards and Technology is not shown on the current cover and is not part of the public hook. Recognition does not authorize a logo, seal, screenshot, portrait, photograph, trademark use or endorsement claim." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "A DIGITAL TWIN BEGINS WITH GAPS.", "The problem: A Digital Twin Begins With Gaps fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 067 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Digital Twin Begins With Gaps can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 067, A Digital Twin Begins With Gaps: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "A DIGITAL TWIN BEGINS WITH GAPS.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/067/build-067-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "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 067, 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 identified or implied." }, { "slide": 2, "stage": "Problem", "copy": [ "A DIGITAL TWIN BEGINS WITH GAPS.", "The problem: A Digital Twin Begins With Gaps fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 067 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Digital Twin Begins With Gaps can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 067, A Digital Twin Begins With Gaps: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The problem: A Digital Twin Begins With Gaps fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “A DIGITAL TWIN BEGINS WITH GAPS.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 067, 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." }, { "slide": 3, "stage": "System", "copy": [ "A DIGITAL TWIN BEGINS WITH GAPS.", "The problem: A Digital Twin Begins With Gaps fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 067 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Digital Twin Begins With Gaps can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 067, A Digital Twin Begins With Gaps: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the A Digital Twin Begins With Gaps mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 067, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "A DIGITAL TWIN BEGINS WITH GAPS.", "The problem: A Digital Twin Begins With Gaps fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 067 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Digital Twin Begins With Gaps can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 067, A Digital Twin Begins With Gaps: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “National Institute of Standards and Technology” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "The official page is relevant context only. It does not make an unspecified image evidence of the build, its outcomes, safety, compliance, effectiveness, or endorsement.", "accessibility": "Slide 4 alt text must identify Build 067, 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://doi.org/10.6028/NIST.CSWP.01162020; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "A DIGITAL TWIN BEGINS WITH GAPS.", "The problem: A Digital Twin Begins With Gaps fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 067 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Digital Twin Begins With Gaps can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 067, A Digital Twin Begins With Gaps: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Demo: walk through one bounded state change in the Build 067 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 067, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 067, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "A DIGITAL TWIN BEGINS WITH GAPS.", "The problem: A Digital Twin Begins With Gaps fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 067 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Digital Twin Begins With Gaps can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 067, A Digital Twin Begins With Gaps: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Implication: A Digital Twin Begins With Gaps can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 067, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "A DIGITAL TWIN BEGINS WITH GAPS.", "The problem: A Digital Twin Begins With Gaps fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: National Institute of Standards and Technology frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 067 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Digital Twin Begins With Gaps can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 067, A Digital Twin Begins With Gaps: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary." ], "headline": "Explore Build 067, A Digital Twin Begins With Gaps: watch the cut, inspect the motion argument, test the interactive prototype, and review its evidence boundary.", "visualGuidance": "Use a quiet RN-owned closing card with Build 067, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 067, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "068", "title": "From Knowing You to Acting for You", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/068/build-068-linkedin-poster.png", "altText": "Build 068, From Knowing You to Acting for You: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST AI Risk Management Framework", "type": "official/primary contextual authority", "relevance": "NIST AI Risk Management Framework is recognizable because its official remit directly frames the domain of From Knowing You to Acting for You; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Institute of Standards and Technology is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "NIST AI Risk Management Framework provides context for the question behind Build 068; the proposition and prototype are RN’s synthesis.", "The problem: From Knowing You to Acting for You fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 068 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Knowing You to Acting for You can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 068: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "NIST AI Risk Management Framework provides context for the question behind Build 068; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/068/build-068-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 068, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "NIST AI Risk Management Framework provides context for the question behind Build 068; the proposition and prototype are RN’s synthesis.", "The problem: From Knowing You to Acting for You fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 068 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Knowing You to Acting for You can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 068: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: From Knowing You to Acting for You fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “NIST AI Risk Management Framework provides context for the question behind Build 068; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 068, 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." }, { "slide": 3, "stage": "System", "copy": [ "NIST AI Risk Management Framework provides context for the question behind Build 068; the proposition and prototype are RN’s synthesis.", "The problem: From Knowing You to Acting for You fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 068 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Knowing You to Acting for You can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 068: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the From Knowing You to Acting for You mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 068, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "NIST AI Risk Management Framework provides context for the question behind Build 068; the proposition and prototype are RN’s synthesis.", "The problem: From Knowing You to Acting for You fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 068 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Knowing You to Acting for You can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 068: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST AI Risk Management Framework” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "AI system governance and human oversight context", "accessibility": "Slide 4 alt text must identify Build 068, 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.nist.gov/itl/ai-risk-management-framework; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "NIST AI Risk Management Framework provides context for the question behind Build 068; the proposition and prototype are RN’s synthesis.", "The problem: From Knowing You to Acting for You fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 068 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Knowing You to Acting for You can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 068: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 068 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 068, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 068, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "NIST AI Risk Management Framework provides context for the question behind Build 068; the proposition and prototype are RN’s synthesis.", "The problem: From Knowing You to Acting for You fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 068 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Knowing You to Acting for You can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 068: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: From Knowing You to Acting for You can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 068, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "NIST AI Risk Management Framework provides context for the question behind Build 068; the proposition and prototype are RN’s synthesis.", "The problem: From Knowing You to Acting for You fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 068 prototype. Show the interaction or decision path, not an invented result.", "Implication: From Knowing You to Acting for You can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 068: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 068: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 068, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 068, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "069", "title": "Enacted Is Not Implemented", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/069/build-069-linkedin-poster.png", "altText": "Build 069, Enacted Is Not Implemented: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Federal Register Document Drafting Handbook", "type": "official/primary contextual authority", "relevance": "Federal Register Document Drafting Handbook is recognizable because its official remit directly frames the domain of Enacted Is Not Implemented; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Office of the Federal Register is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Federal Register Document Drafting Handbook provides context for the question behind Build 069; the proposition and prototype are RN’s synthesis.", "The problem: Enacted Is Not Implemented fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register Document Drafting Handbook frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 069 prototype. Show the interaction or decision path, not an invented result.", "Implication: Enacted Is Not Implemented can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 069: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Federal Register Document Drafting Handbook provides context for the question behind Build 069; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/069/build-069-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 069, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "Federal Register Document Drafting Handbook provides context for the question behind Build 069; the proposition and prototype are RN’s synthesis.", "The problem: Enacted Is Not Implemented fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register Document Drafting Handbook frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 069 prototype. Show the interaction or decision path, not an invented result.", "Implication: Enacted Is Not Implemented can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 069: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Enacted Is Not Implemented fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Federal Register Document Drafting Handbook provides context for the question behind Build 069; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 069, 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." }, { "slide": 3, "stage": "System", "copy": [ "Federal Register Document Drafting Handbook provides context for the question behind Build 069; the proposition and prototype are RN’s synthesis.", "The problem: Enacted Is Not Implemented fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register Document Drafting Handbook frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 069 prototype. Show the interaction or decision path, not an invented result.", "Implication: Enacted Is Not Implemented can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 069: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Enacted Is Not Implemented mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 069, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Federal Register Document Drafting Handbook provides context for the question behind Build 069; the proposition and prototype are RN’s synthesis.", "The problem: Enacted Is Not Implemented fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register Document Drafting Handbook frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 069 prototype. Show the interaction or decision path, not an invented result.", "Implication: Enacted Is Not Implemented can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 069: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: Federal Register Document Drafting Handbook frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Federal Register Document Drafting Handbook” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Federal rulemaking publication and implementation context", "accessibility": "Slide 4 alt text must identify Build 069, 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.archives.gov/federal-register/write/handbook; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Federal Register Document Drafting Handbook provides context for the question behind Build 069; the proposition and prototype are RN’s synthesis.", "The problem: Enacted Is Not Implemented fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register Document Drafting Handbook frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 069 prototype. Show the interaction or decision path, not an invented result.", "Implication: Enacted Is Not Implemented can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 069: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 069 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 069, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 069, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Federal Register Document Drafting Handbook provides context for the question behind Build 069; the proposition and prototype are RN’s synthesis.", "The problem: Enacted Is Not Implemented fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register Document Drafting Handbook frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 069 prototype. Show the interaction or decision path, not an invented result.", "Implication: Enacted Is Not Implemented can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 069: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Enacted Is Not Implemented can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 069, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Federal Register Document Drafting Handbook provides context for the question behind Build 069; the proposition and prototype are RN’s synthesis.", "The problem: Enacted Is Not Implemented fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register Document Drafting Handbook frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 069 prototype. Show the interaction or decision path, not an invented result.", "Implication: Enacted Is Not Implemented can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 069: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 069: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 069, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 069, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "070", "title": "Legalization Is a Lifecycle, Not a Vote", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/070/build-070-linkedin-poster.png", "altText": "Build 070, Legalization Is a Lifecycle, Not a Vote: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "The Federal Rulemaking Process", "type": "official/primary contextual authority", "relevance": "The Federal Rulemaking Process is recognizable because its official remit directly frames the domain of Legalization Is a Lifecycle, Not a Vote; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Federal Register / National Archives is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 070; the proposition and prototype are RN’s synthesis.", "The problem: Legalization Is a Lifecycle, Not a Vote fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 070 prototype. Show the interaction or decision path, not an invented result.", "Implication: Legalization Is a Lifecycle, Not a Vote can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 070: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The Federal Rulemaking Process provides context for the question behind Build 070; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/070/build-070-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 070, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 070; the proposition and prototype are RN’s synthesis.", "The problem: Legalization Is a Lifecycle, Not a Vote fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 070 prototype. Show the interaction or decision path, not an invented result.", "Implication: Legalization Is a Lifecycle, Not a Vote can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 070: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Legalization Is a Lifecycle, Not a Vote fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “The Federal Rulemaking Process provides context for the question behind Build 070; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 070, 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." }, { "slide": 3, "stage": "System", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 070; the proposition and prototype are RN’s synthesis.", "The problem: Legalization Is a Lifecycle, Not a Vote fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 070 prototype. Show the interaction or decision path, not an invented result.", "Implication: Legalization Is a Lifecycle, Not a Vote can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 070: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Legalization Is a Lifecycle, Not a Vote mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 070, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 070; the proposition and prototype are RN’s synthesis.", "The problem: Legalization Is a Lifecycle, Not a Vote fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 070 prototype. Show the interaction or decision path, not an invented result.", "Implication: Legalization Is a Lifecycle, Not a Vote can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 070: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “The Federal Rulemaking Process” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Rulemaking lifecycle context; not evidence of any jurisdiction’s legalization outcome", "accessibility": "Slide 4 alt text must identify Build 070, 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.federalregister.gov/reader-aids/the-federal-register/the-rulemaking-process; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 070; the proposition and prototype are RN’s synthesis.", "The problem: Legalization Is a Lifecycle, Not a Vote fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 070 prototype. Show the interaction or decision path, not an invented result.", "Implication: Legalization Is a Lifecycle, Not a Vote can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 070: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 070 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 070, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 070, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 070; the proposition and prototype are RN’s synthesis.", "The problem: Legalization Is a Lifecycle, Not a Vote fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 070 prototype. Show the interaction or decision path, not an invented result.", "Implication: Legalization Is a Lifecycle, Not a Vote can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 070: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Legalization Is a Lifecycle, Not a Vote can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 070, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 070; the proposition and prototype are RN’s synthesis.", "The problem: Legalization Is a Lifecycle, Not a Vote fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 070 prototype. Show the interaction or decision path, not an invented result.", "Implication: Legalization Is a Lifecycle, Not a Vote can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 070: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 070: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 070, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 070, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "071", "title": "Fictional Medical-Cannabis Access Gates", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/071/build-071-linkedin-poster.png", "altText": "Build 071, Fictional Medical-Cannabis Access Gates: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Medical Cannabis Registry Program", "type": "official/primary contextual authority", "relevance": "Medical Cannabis Registry Program is recognizable because its official remit directly frames the domain of Fictional Medical-Cannabis Access Gates; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Hawai‘i Department of Health is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Medical Cannabis Registry Program provides context for the question behind Build 071; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Medical-Cannabis Access Gates fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Medical Cannabis Registry Program frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 071 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Medical-Cannabis Access Gates can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 071: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Medical Cannabis Registry Program provides context for the question behind Build 071; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/071/build-071-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 071, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "Medical Cannabis Registry Program provides context for the question behind Build 071; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Medical-Cannabis Access Gates fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Medical Cannabis Registry Program frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 071 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Medical-Cannabis Access Gates can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 071: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Fictional Medical-Cannabis Access Gates fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Medical Cannabis Registry Program provides context for the question behind Build 071; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 071, 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." }, { "slide": 3, "stage": "System", "copy": [ "Medical Cannabis Registry Program provides context for the question behind Build 071; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Medical-Cannabis Access Gates fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Medical Cannabis Registry Program frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 071 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Medical-Cannabis Access Gates can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 071: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Fictional Medical-Cannabis Access Gates mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 071, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Medical Cannabis Registry Program provides context for the question behind Build 071; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Medical-Cannabis Access Gates fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Medical Cannabis Registry Program frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 071 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Medical-Cannabis Access Gates can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 071: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: Medical Cannabis Registry Program frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Medical Cannabis Registry Program” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Real program context only; build records and gates remain explicitly fictional/synthetic", "accessibility": "Slide 4 alt text must identify Build 071, 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://health.hawaii.gov/medicalcannabis/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Medical Cannabis Registry Program provides context for the question behind Build 071; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Medical-Cannabis Access Gates fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Medical Cannabis Registry Program frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 071 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Medical-Cannabis Access Gates can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 071: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 071 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 071, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 071, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Medical Cannabis Registry Program provides context for the question behind Build 071; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Medical-Cannabis Access Gates fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Medical Cannabis Registry Program frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 071 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Medical-Cannabis Access Gates can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 071: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Fictional Medical-Cannabis Access Gates can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 071, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Medical Cannabis Registry Program provides context for the question behind Build 071; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Medical-Cannabis Access Gates fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Medical Cannabis Registry Program frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 071 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Medical-Cannabis Access Gates can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 071: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 071: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 071, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 071, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "072", "title": "Fictional Island Access Comparison", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/072/build-072-linkedin-poster.png", "altText": "Build 072, Fictional Island Access Comparison: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Supply Chain Resilience Guide", "type": "official/primary contextual authority", "relevance": "Supply Chain Resilience Guide is recognizable because its official remit directly frames the domain of Fictional Island Access Comparison; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Federal Emergency Management Agency is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Supply Chain Resilience Guide provides context for the question behind Build 072; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Island Access Comparison fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 072 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Island Access Comparison can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 072: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Supply Chain Resilience Guide provides context for the question behind Build 072; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/072/build-072-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 072, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "Supply Chain Resilience Guide provides context for the question behind Build 072; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Island Access Comparison fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 072 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Island Access Comparison can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 072: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Fictional Island Access Comparison fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Supply Chain Resilience Guide provides context for the question behind Build 072; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 072, 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." }, { "slide": 3, "stage": "System", "copy": [ "Supply Chain Resilience Guide provides context for the question behind Build 072; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Island Access Comparison fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 072 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Island Access Comparison can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 072: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Fictional Island Access Comparison mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 072, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Supply Chain Resilience Guide provides context for the question behind Build 072; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Island Access Comparison fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 072 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Island Access Comparison can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 072: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Supply Chain Resilience Guide” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Resilience-planning context only; fictional island comparison is RN synthesis", "accessibility": "Slide 4 alt text must identify Build 072, 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.fema.gov/emergency-managers/risk-management/building-science/supply-chain-resilience-guide; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Supply Chain Resilience Guide provides context for the question behind Build 072; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Island Access Comparison fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 072 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Island Access Comparison can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 072: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 072 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 072, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 072, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Supply Chain Resilience Guide provides context for the question behind Build 072; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Island Access Comparison fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 072 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Island Access Comparison can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 072: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Fictional Island Access Comparison can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 072, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Supply Chain Resilience Guide provides context for the question behind Build 072; the proposition and prototype are RN’s synthesis.", "The problem: Fictional Island Access Comparison fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 072 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Island Access Comparison can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 072: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 072: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 072, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 072, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "073", "title": "Access for Whom?", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/073/build-073-linkedin-poster.png", "altText": "Build 073, Access for Whom?: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "CDC Program Evaluation Framework", "type": "official/primary contextual authority", "relevance": "CDC Program Evaluation Framework is recognizable because its official remit directly frames the domain of Access for Whom?; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Centers for Disease Control and Prevention is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 073; the proposition and prototype are RN’s synthesis.", "The problem: Access for Whom? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 073 prototype. Show the interaction or decision path, not an invented result.", "Implication: Access for Whom? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 073: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "CDC Program Evaluation Framework provides context for the question behind Build 073; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/073/build-073-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 073, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 073; the proposition and prototype are RN’s synthesis.", "The problem: Access for Whom? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 073 prototype. Show the interaction or decision path, not an invented result.", "Implication: Access for Whom? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 073: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Access for Whom? fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “CDC Program Evaluation Framework provides context for the question behind Build 073; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 073, 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." }, { "slide": 3, "stage": "System", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 073; the proposition and prototype are RN’s synthesis.", "The problem: Access for Whom? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 073 prototype. Show the interaction or decision path, not an invented result.", "Implication: Access for Whom? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 073: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Access for Whom? mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 073, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 073; the proposition and prototype are RN’s synthesis.", "The problem: Access for Whom? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 073 prototype. Show the interaction or decision path, not an invented result.", "Implication: Access for Whom? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 073: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “CDC Program Evaluation Framework” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Stakeholder and context evaluation; not proof of equitable access", "accessibility": "Slide 4 alt text must identify Build 073, 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.cdc.gov/mmwr/volumes/73/rr/rr7306a1.htm; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 073; the proposition and prototype are RN’s synthesis.", "The problem: Access for Whom? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 073 prototype. Show the interaction or decision path, not an invented result.", "Implication: Access for Whom? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 073: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 073 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 073, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 073, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 073; the proposition and prototype are RN’s synthesis.", "The problem: Access for Whom? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 073 prototype. Show the interaction or decision path, not an invented result.", "Implication: Access for Whom? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 073: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Access for Whom? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 073, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 073; the proposition and prototype are RN’s synthesis.", "The problem: Access for Whom? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 073 prototype. Show the interaction or decision path, not an invented result.", "Implication: Access for Whom? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 073: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 073: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 073, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 073, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "074", "title": "The Law Says Yes. The System Says Not Yet.", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/074/build-074-linkedin-poster.png", "altText": "Build 074, The Law Says Yes. The System Says Not Yet.: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "The Federal Rulemaking Process", "type": "official/primary contextual authority", "relevance": "The Federal Rulemaking Process is recognizable because its official remit directly frames the domain of The Law Says Yes. The System Says Not Yet.; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Federal Register / National Archives is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 074; the proposition and prototype are RN’s synthesis.", "The problem: The Law Says Yes. The System Says Not Yet. fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 074 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Law Says Yes. The System Says Not Yet. can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 074: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The Federal Rulemaking Process provides context for the question behind Build 074; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/074/build-074-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 074, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 074; the proposition and prototype are RN’s synthesis.", "The problem: The Law Says Yes. The System Says Not Yet. fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 074 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Law Says Yes. The System Says Not Yet. can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 074: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: The Law Says Yes. The System Says Not Yet. fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “The Federal Rulemaking Process provides context for the question behind Build 074; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 074, 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." }, { "slide": 3, "stage": "System", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 074; the proposition and prototype are RN’s synthesis.", "The problem: The Law Says Yes. The System Says Not Yet. fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 074 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Law Says Yes. The System Says Not Yet. can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 074: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Law Says Yes. The System Says Not Yet. mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 074, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 074; the proposition and prototype are RN’s synthesis.", "The problem: The Law Says Yes. The System Says Not Yet. fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 074 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Law Says Yes. The System Says Not Yet. can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 074: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “The Federal Rulemaking Process” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Formal rulemaking stages; not proof of a specific implementation gap", "accessibility": "Slide 4 alt text must identify Build 074, 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.federalregister.gov/reader-aids/the-federal-register/the-rulemaking-process; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 074; the proposition and prototype are RN’s synthesis.", "The problem: The Law Says Yes. The System Says Not Yet. fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 074 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Law Says Yes. The System Says Not Yet. can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 074: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 074 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 074, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 074, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 074; the proposition and prototype are RN’s synthesis.", "The problem: The Law Says Yes. The System Says Not Yet. fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 074 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Law Says Yes. The System Says Not Yet. can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 074: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: The Law Says Yes. The System Says Not Yet. can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 074, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 074; the proposition and prototype are RN’s synthesis.", "The problem: The Law Says Yes. The System Says Not Yet. fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 074 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Law Says Yes. The System Says Not Yet. can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 074: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 074: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 074, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 074, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "075", "title": "Same Goal, Different Regulatory Machine", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/075/build-075-linkedin-poster.png", "altText": "Build 075, Same Goal, Different Regulatory Machine: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Regulations.gov About", "type": "official/primary contextual authority", "relevance": "Regulations.gov About is recognizable because its official remit directly frames the domain of Same Goal, Different Regulatory Machine; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by U.S. General Services Administration / eRulemaking Program is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Regulations.gov About provides context for the question behind Build 075; the proposition and prototype are RN’s synthesis.", "The problem: Same Goal, Different Regulatory Machine fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulations.gov About frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 075 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Goal, Different Regulatory Machine can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 075: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Regulations.gov About provides context for the question behind Build 075; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/075/build-075-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 075, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "Regulations.gov About provides context for the question behind Build 075; the proposition and prototype are RN’s synthesis.", "The problem: Same Goal, Different Regulatory Machine fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulations.gov About frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 075 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Goal, Different Regulatory Machine can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 075: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Same Goal, Different Regulatory Machine fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Regulations.gov About provides context for the question behind Build 075; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 075, 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." }, { "slide": 3, "stage": "System", "copy": [ "Regulations.gov About provides context for the question behind Build 075; the proposition and prototype are RN’s synthesis.", "The problem: Same Goal, Different Regulatory Machine fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulations.gov About frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 075 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Goal, Different Regulatory Machine can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 075: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Same Goal, Different Regulatory Machine mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 075, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Regulations.gov About provides context for the question behind Build 075; the proposition and prototype are RN’s synthesis.", "The problem: Same Goal, Different Regulatory Machine fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulations.gov About frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 075 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Goal, Different Regulatory Machine can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 075: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: Regulations.gov About frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Regulations.gov About” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Regulatory-system comparison context; does not establish equivalence or outcomes", "accessibility": "Slide 4 alt text must identify Build 075, 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.regulations.gov/about; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Regulations.gov About provides context for the question behind Build 075; the proposition and prototype are RN’s synthesis.", "The problem: Same Goal, Different Regulatory Machine fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulations.gov About frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 075 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Goal, Different Regulatory Machine can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 075: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 075 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 075, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 075, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Regulations.gov About provides context for the question behind Build 075; the proposition and prototype are RN’s synthesis.", "The problem: Same Goal, Different Regulatory Machine fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulations.gov About frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 075 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Goal, Different Regulatory Machine can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 075: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Same Goal, Different Regulatory Machine can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 075, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Regulations.gov About provides context for the question behind Build 075; the proposition and prototype are RN’s synthesis.", "The problem: Same Goal, Different Regulatory Machine fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Regulations.gov About frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 075 prototype. Show the interaction or decision path, not an invented result.", "Implication: Same Goal, Different Regulatory Machine can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 075: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 075: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 075, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 075, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "076", "title": "The Map That Knows the Difference Between Similar Laws", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/076/build-076-linkedin-poster.png", "altText": "Build 076, The Map That Knows the Difference Between Similar Laws: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Congress.gov Legislation Help", "type": "official/primary contextual authority", "relevance": "Congress.gov Legislation Help is recognizable because its official remit directly frames the domain of The Map That Knows the Difference Between Similar Laws; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Library of Congress is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Congress.gov Legislation Help provides context for the question behind Build 076; the proposition and prototype are RN’s synthesis.", "The problem: The Map That Knows the Difference Between Similar Laws fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Congress.gov Legislation Help frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 076 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Map That Knows the Difference Between Similar Laws can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 076: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Congress.gov Legislation Help provides context for the question behind Build 076; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/076/build-076-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 076, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "Congress.gov Legislation Help provides context for the question behind Build 076; the proposition and prototype are RN’s synthesis.", "The problem: The Map That Knows the Difference Between Similar Laws fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Congress.gov Legislation Help frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 076 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Map That Knows the Difference Between Similar Laws can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 076: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: The Map That Knows the Difference Between Similar Laws fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Congress.gov Legislation Help provides context for the question behind Build 076; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 076, 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." }, { "slide": 3, "stage": "System", "copy": [ "Congress.gov Legislation Help provides context for the question behind Build 076; the proposition and prototype are RN’s synthesis.", "The problem: The Map That Knows the Difference Between Similar Laws fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Congress.gov Legislation Help frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 076 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Map That Knows the Difference Between Similar Laws can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 076: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Map That Knows the Difference Between Similar Laws mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 076, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Congress.gov Legislation Help provides context for the question behind Build 076; the proposition and prototype are RN’s synthesis.", "The problem: The Map That Knows the Difference Between Similar Laws fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Congress.gov Legislation Help frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 076 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Map That Knows the Difference Between Similar Laws can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 076: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: Congress.gov Legislation Help frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Congress.gov Legislation Help” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Legislative metadata and status context; map and comparisons remain RN synthesis", "accessibility": "Slide 4 alt text must identify Build 076, 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.congress.gov/help/legislation; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Congress.gov Legislation Help provides context for the question behind Build 076; the proposition and prototype are RN’s synthesis.", "The problem: The Map That Knows the Difference Between Similar Laws fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Congress.gov Legislation Help frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 076 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Map That Knows the Difference Between Similar Laws can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 076: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 076 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 076, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 076, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Congress.gov Legislation Help provides context for the question behind Build 076; the proposition and prototype are RN’s synthesis.", "The problem: The Map That Knows the Difference Between Similar Laws fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Congress.gov Legislation Help frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 076 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Map That Knows the Difference Between Similar Laws can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 076: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: The Map That Knows the Difference Between Similar Laws can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 076, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Congress.gov Legislation Help provides context for the question behind Build 076; the proposition and prototype are RN’s synthesis.", "The problem: The Map That Knows the Difference Between Similar Laws fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Congress.gov Legislation Help frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 076 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Map That Knows the Difference Between Similar Laws can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 076: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 076: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 076, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 076, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "077", "title": "What Does This Change Actually Do?", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/077/build-077-linkedin-poster.png", "altText": "Build 077, What Does This Change Actually Do?: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "The Federal Rulemaking Process", "type": "official/primary contextual authority", "relevance": "The Federal Rulemaking Process is recognizable because its official remit directly frames the domain of What Does This Change Actually Do?; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Federal Register / National Archives is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 077; the proposition and prototype are RN’s synthesis.", "The problem: What Does This Change Actually Do? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 077 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Does This Change Actually Do? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 077: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The Federal Rulemaking Process provides context for the question behind Build 077; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/077/build-077-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 077, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 077; the proposition and prototype are RN’s synthesis.", "The problem: What Does This Change Actually Do? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 077 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Does This Change Actually Do? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 077: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: What Does This Change Actually Do? fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “The Federal Rulemaking Process provides context for the question behind Build 077; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 077, 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." }, { "slide": 3, "stage": "System", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 077; the proposition and prototype are RN’s synthesis.", "The problem: What Does This Change Actually Do? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 077 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Does This Change Actually Do? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 077: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the What Does This Change Actually Do? mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 077, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 077; the proposition and prototype are RN’s synthesis.", "The problem: What Does This Change Actually Do? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 077 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Does This Change Actually Do? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 077: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “The Federal Rulemaking Process” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Rule-change mechanism context; not evidence of predicted effects", "accessibility": "Slide 4 alt text must identify Build 077, 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.federalregister.gov/reader-aids/the-federal-register/the-rulemaking-process; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 077; the proposition and prototype are RN’s synthesis.", "The problem: What Does This Change Actually Do? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 077 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Does This Change Actually Do? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 077: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 077 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 077, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 077, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 077; the proposition and prototype are RN’s synthesis.", "The problem: What Does This Change Actually Do? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 077 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Does This Change Actually Do? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 077: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: What Does This Change Actually Do? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 077, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "The Federal Rulemaking Process provides context for the question behind Build 077; the proposition and prototype are RN’s synthesis.", "The problem: What Does This Change Actually Do? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: The Federal Rulemaking Process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 077 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Does This Change Actually Do? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 077: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 077: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 077, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 077, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "078", "title": "Evidence Does Not Travel Intact by Accident", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/078/build-078-linkedin-poster.png", "altText": "Build 078, Evidence Does Not Travel Intact by Accident: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "PubMed User Guide", "type": "official/primary contextual authority", "relevance": "PubMed User Guide is recognizable because its official remit directly frames the domain of Evidence Does Not Travel Intact by Accident; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Library of Medicine is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "PubMed User Guide provides context for the question behind Build 078; the proposition and prototype are RN’s synthesis.", "The problem: Evidence Does Not Travel Intact by Accident fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 078 prototype. Show the interaction or decision path, not an invented result.", "Implication: Evidence Does Not Travel Intact by Accident can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 078: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "PubMed User Guide provides context for the question behind Build 078; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/078/build-078-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 078, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "PubMed User Guide provides context for the question behind Build 078; the proposition and prototype are RN’s synthesis.", "The problem: Evidence Does Not Travel Intact by Accident fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 078 prototype. Show the interaction or decision path, not an invented result.", "Implication: Evidence Does Not Travel Intact by Accident can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 078: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Evidence Does Not Travel Intact by Accident fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “PubMed User Guide provides context for the question behind Build 078; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 078, 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." }, { "slide": 3, "stage": "System", "copy": [ "PubMed User Guide provides context for the question behind Build 078; the proposition and prototype are RN’s synthesis.", "The problem: Evidence Does Not Travel Intact by Accident fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 078 prototype. Show the interaction or decision path, not an invented result.", "Implication: Evidence Does Not Travel Intact by Accident can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 078: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Evidence Does Not Travel Intact by Accident mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 078, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "PubMed User Guide provides context for the question behind Build 078; the proposition and prototype are RN’s synthesis.", "The problem: Evidence Does Not Travel Intact by Accident fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 078 prototype. Show the interaction or decision path, not an invented result.", "Implication: Evidence Does Not Travel Intact by Accident can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 078: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “PubMed User Guide” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Bibliographic retrieval context; not proof that interpretation remains intact", "accessibility": "Slide 4 alt text must identify Build 078, 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://pubmed.ncbi.nlm.nih.gov/help/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "PubMed User Guide provides context for the question behind Build 078; the proposition and prototype are RN’s synthesis.", "The problem: Evidence Does Not Travel Intact by Accident fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 078 prototype. Show the interaction or decision path, not an invented result.", "Implication: Evidence Does Not Travel Intact by Accident can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 078: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 078 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 078, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 078, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "PubMed User Guide provides context for the question behind Build 078; the proposition and prototype are RN’s synthesis.", "The problem: Evidence Does Not Travel Intact by Accident fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 078 prototype. Show the interaction or decision path, not an invented result.", "Implication: Evidence Does Not Travel Intact by Accident can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 078: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Evidence Does Not Travel Intact by Accident can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 078, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "PubMed User Guide provides context for the question behind Build 078; the proposition and prototype are RN’s synthesis.", "The problem: Evidence Does Not Travel Intact by Accident fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 078 prototype. Show the interaction or decision path, not an invented result.", "Implication: Evidence Does Not Travel Intact by Accident can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 078: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 078: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 078, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 078, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "079", "title": "A Search Result Is Not an Evidence Map", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/079/build-079-linkedin-poster.png", "altText": "Build 079, A Search Result Is Not an Evidence Map: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "PubMed User Guide", "type": "official/primary contextual authority", "relevance": "PubMed User Guide is recognizable because its official remit directly frames the domain of A Search Result Is Not an Evidence Map; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Library of Medicine is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "PubMed User Guide provides context for the question behind Build 079; the proposition and prototype are RN’s synthesis.", "The problem: A Search Result Is Not an Evidence Map fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 079 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Search Result Is Not an Evidence Map can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 079: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "PubMed User Guide provides context for the question behind Build 079; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/079/build-079-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 079, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "PubMed User Guide provides context for the question behind Build 079; the proposition and prototype are RN’s synthesis.", "The problem: A Search Result Is Not an Evidence Map fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 079 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Search Result Is Not an Evidence Map can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 079: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: A Search Result Is Not an Evidence Map fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “PubMed User Guide provides context for the question behind Build 079; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 079, 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." }, { "slide": 3, "stage": "System", "copy": [ "PubMed User Guide provides context for the question behind Build 079; the proposition and prototype are RN’s synthesis.", "The problem: A Search Result Is Not an Evidence Map fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 079 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Search Result Is Not an Evidence Map can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 079: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the A Search Result Is Not an Evidence Map mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 079, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "PubMed User Guide provides context for the question behind Build 079; the proposition and prototype are RN’s synthesis.", "The problem: A Search Result Is Not an Evidence Map fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 079 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Search Result Is Not an Evidence Map can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 079: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “PubMed User Guide” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Search and record structure context; evidence-map design is RN synthesis", "accessibility": "Slide 4 alt text must identify Build 079, 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://pubmed.ncbi.nlm.nih.gov/help/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "PubMed User Guide provides context for the question behind Build 079; the proposition and prototype are RN’s synthesis.", "The problem: A Search Result Is Not an Evidence Map fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 079 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Search Result Is Not an Evidence Map can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 079: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 079 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 079, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 079, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "PubMed User Guide provides context for the question behind Build 079; the proposition and prototype are RN’s synthesis.", "The problem: A Search Result Is Not an Evidence Map fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 079 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Search Result Is Not an Evidence Map can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 079: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: A Search Result Is Not an Evidence Map can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 079, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "PubMed User Guide provides context for the question behind Build 079; the proposition and prototype are RN’s synthesis.", "The problem: A Search Result Is Not an Evidence Map fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: PubMed User Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 079 prototype. Show the interaction or decision path, not an invented result.", "Implication: A Search Result Is Not an Evidence Map can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 079: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 079: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 079, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 079, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "080", "title": "The Article Was Only the First Output", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/080/build-080-linkedin-poster.png", "altText": "Build 080, The Article Was Only the First Output: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. Web Design System documentation", "type": "official/primary contextual authority", "relevance": "U.S. Web Design System documentation is recognizable because its official remit directly frames the domain of The Article Was Only the First Output; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by General Services Administration is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "U.S. Web Design System documentation provides context for the question behind Build 080; the proposition and prototype are RN’s synthesis.", "The problem: The Article Was Only the First Output fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System documentation frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 080 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Article Was Only the First Output can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 080: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "U.S. Web Design System documentation provides context for the question behind Build 080; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/080/build-080-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 080, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "U.S. Web Design System documentation provides context for the question behind Build 080; the proposition and prototype are RN’s synthesis.", "The problem: The Article Was Only the First Output fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System documentation frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 080 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Article Was Only the First Output can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 080: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: The Article Was Only the First Output fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “U.S. Web Design System documentation provides context for the question behind Build 080; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 080, 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." }, { "slide": 3, "stage": "System", "copy": [ "U.S. Web Design System documentation provides context for the question behind Build 080; the proposition and prototype are RN’s synthesis.", "The problem: The Article Was Only the First Output fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System documentation frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 080 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Article Was Only the First Output can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 080: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the The Article Was Only the First Output mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 080, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "U.S. Web Design System documentation provides context for the question behind Build 080; the proposition and prototype are RN’s synthesis.", "The problem: The Article Was Only the First Output fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System documentation frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 080 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Article Was Only the First Output can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 080: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: U.S. Web Design System documentation frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. Web Design System documentation” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Public-service publishing context; not proof of distribution performance", "accessibility": "Slide 4 alt text must identify Build 080, 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://designsystem.digital.gov/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "U.S. Web Design System documentation provides context for the question behind Build 080; the proposition and prototype are RN’s synthesis.", "The problem: The Article Was Only the First Output fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System documentation frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 080 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Article Was Only the First Output can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 080: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 080 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 080, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 080, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "U.S. Web Design System documentation provides context for the question behind Build 080; the proposition and prototype are RN’s synthesis.", "The problem: The Article Was Only the First Output fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System documentation frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 080 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Article Was Only the First Output can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 080: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: The Article Was Only the First Output can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 080, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "U.S. Web Design System documentation provides context for the question behind Build 080; the proposition and prototype are RN’s synthesis.", "The problem: The Article Was Only the First Output fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System documentation frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 080 prototype. Show the interaction or decision path, not an invented result.", "Implication: The Article Was Only the First Output can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 080: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 080: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 080, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 080, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "081", "title": "What Might People Be Struggling With?", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/081/build-081-linkedin-poster.png", "altText": "Build 081, What Might People Be Struggling With?: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "CDC Program Evaluation Framework", "type": "official/primary contextual authority", "relevance": "CDC Program Evaluation Framework is recognizable because its official remit directly frames the domain of What Might People Be Struggling With?; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Centers for Disease Control and Prevention is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 081; the proposition and prototype are RN’s synthesis.", "The problem: What Might People Be Struggling With? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 081 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Might People Be Struggling With? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 081: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "CDC Program Evaluation Framework provides context for the question behind Build 081; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/081/build-081-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 081, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 081; the proposition and prototype are RN’s synthesis.", "The problem: What Might People Be Struggling With? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 081 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Might People Be Struggling With? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 081: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: What Might People Be Struggling With? fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “CDC Program Evaluation Framework provides context for the question behind Build 081; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 081, 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." }, { "slide": 3, "stage": "System", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 081; the proposition and prototype are RN’s synthesis.", "The problem: What Might People Be Struggling With? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 081 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Might People Be Struggling With? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 081: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the What Might People Be Struggling With? mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 081, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 081; the proposition and prototype are RN’s synthesis.", "The problem: What Might People Be Struggling With? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 081 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Might People Be Struggling With? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 081: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “CDC Program Evaluation Framework” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Stakeholder inquiry context; portrayed needs remain synthetic and not community testimony", "accessibility": "Slide 4 alt text must identify Build 081, 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.cdc.gov/mmwr/volumes/73/rr/rr7306a1.htm; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 081; the proposition and prototype are RN’s synthesis.", "The problem: What Might People Be Struggling With? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 081 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Might People Be Struggling With? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 081: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 081 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 081, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 081, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 081; the proposition and prototype are RN’s synthesis.", "The problem: What Might People Be Struggling With? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 081 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Might People Be Struggling With? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 081: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: What Might People Be Struggling With? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 081, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "CDC Program Evaluation Framework provides context for the question behind Build 081; the proposition and prototype are RN’s synthesis.", "The problem: What Might People Be Struggling With? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Program Evaluation Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 081 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Might People Be Struggling With? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 081: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 081: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 081, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 081, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "082", "title": "An Audience Is Not a Demographic Box", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/082/build-082-linkedin-poster.png", "altText": "Build 082, An Audience Is Not a Demographic Box: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "About the Census Bureau", "type": "official/primary contextual authority", "relevance": "About the Census Bureau is recognizable because its official remit directly frames the domain of An Audience Is Not a Demographic Box; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by U.S. Census Bureau is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "About the Census Bureau provides context for the question behind Build 082; the proposition and prototype are RN’s synthesis.", "The problem: An Audience Is Not a Demographic Box fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: About the Census Bureau frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 082 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Audience Is Not a Demographic Box can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 082: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "About the Census Bureau provides context for the question behind Build 082; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/082/build-082-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 082, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "About the Census Bureau provides context for the question behind Build 082; the proposition and prototype are RN’s synthesis.", "The problem: An Audience Is Not a Demographic Box fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: About the Census Bureau frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 082 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Audience Is Not a Demographic Box can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 082: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: An Audience Is Not a Demographic Box fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “About the Census Bureau provides context for the question behind Build 082; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 082, 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." }, { "slide": 3, "stage": "System", "copy": [ "About the Census Bureau provides context for the question behind Build 082; the proposition and prototype are RN’s synthesis.", "The problem: An Audience Is Not a Demographic Box fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: About the Census Bureau frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 082 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Audience Is Not a Demographic Box can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 082: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the An Audience Is Not a Demographic Box mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 082, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "About the Census Bureau provides context for the question behind Build 082; the proposition and prototype are RN’s synthesis.", "The problem: An Audience Is Not a Demographic Box fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: About the Census Bureau frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 082 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Audience Is Not a Demographic Box can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 082: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: About the Census Bureau frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “About the Census Bureau” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Population-statistics context; audience strategy and personas remain RN synthesis", "accessibility": "Slide 4 alt text must identify Build 082, 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.census.gov/about.html; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "About the Census Bureau provides context for the question behind Build 082; the proposition and prototype are RN’s synthesis.", "The problem: An Audience Is Not a Demographic Box fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: About the Census Bureau frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 082 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Audience Is Not a Demographic Box can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 082: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 082 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 082, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 082, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "About the Census Bureau provides context for the question behind Build 082; the proposition and prototype are RN’s synthesis.", "The problem: An Audience Is Not a Demographic Box fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: About the Census Bureau frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 082 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Audience Is Not a Demographic Box can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 082: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: An Audience Is Not a Demographic Box can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 082, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "About the Census Bureau provides context for the question behind Build 082; the proposition and prototype are RN’s synthesis.", "The problem: An Audience Is Not a Demographic Box fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: About the Census Bureau frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 082 prototype. Show the interaction or decision path, not an invented result.", "Implication: An Audience Is Not a Demographic Box can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 082: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 082: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 082, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 082, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "083", "title": "Your Work Is Already Full of Content", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/083/build-083-linkedin-poster.png", "altText": "Build 083, Your Work Is Already Full of Content: creator-owned typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST Privacy Framework", "type": "official/primary contextual authority", "relevance": "NIST Privacy Framework is recognizable because its official remit directly frames the domain of Your Work Is Already Full of Content; recognition is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Institute of Standards and Technology is claimed. Institutional recognition does not authorize a logo, seal, screenshot, photograph, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "NIST Privacy Framework provides context for the question behind Build 083; the proposition and prototype are RN’s synthesis.", "The problem: Your Work Is Already Full of Content fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 083 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Work Is Already Full of Content can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 083: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "NIST Privacy Framework provides context for the question behind Build 083; the proposition and prototype are RN’s synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/083/build-083-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Supports build identity and RN proposition only; it is not documentary evidence and does not imply institutional endorsement.", "accessibility": "Slide 1 alt text must identify Build 083, 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 used." }, { "slide": 2, "stage": "Problem", "copy": [ "NIST Privacy Framework provides context for the question behind Build 083; the proposition and prototype are RN’s synthesis.", "The problem: Your Work Is Already Full of Content fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 083 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Work Is Already Full of Content can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 083: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Your Work Is Already Full of Content fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “NIST Privacy Framework provides context for the question behind Build 083; the proposition and prototype are RN’s synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 083, 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." }, { "slide": 3, "stage": "System", "copy": [ "NIST Privacy Framework provides context for the question behind Build 083; the proposition and prototype are RN’s synthesis.", "The problem: Your Work Is Already Full of Content fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 083 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Work Is Already Full of Content can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 083: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Your Work Is Already Full of Content mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 083, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "NIST Privacy Framework provides context for the question behind Build 083; the proposition and prototype are RN’s synthesis.", "The problem: Your Work Is Already Full of Content fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 083 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Work Is Already Full of Content can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 083: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST Privacy Framework” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Privacy-risk context for reusing work artifacts; not proof that any content is publication-ready", "accessibility": "Slide 4 alt text must identify Build 083, 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.nist.gov/privacy-framework; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "NIST Privacy Framework provides context for the question behind Build 083; the proposition and prototype are RN’s synthesis.", "The problem: Your Work Is Already Full of Content fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 083 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Work Is Already Full of Content can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 083: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 083 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 083, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 083, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "NIST Privacy Framework provides context for the question behind Build 083; the proposition and prototype are RN’s synthesis.", "The problem: Your Work Is Already Full of Content fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 083 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Work Is Already Full of Content can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 083: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Your Work Is Already Full of Content can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 083, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "NIST Privacy Framework provides context for the question behind Build 083; the proposition and prototype are RN’s synthesis.", "The problem: Your Work Is Already Full of Content fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 083 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Work Is Already Full of Content can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 083: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 083: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 083, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 083, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "084", "title": "Who Created the Value—and Who Gets It?", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/084/build-084-linkedin-poster.png", "altText": "Build 084, Who Created the Value—and Who Gets It?: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. Copyright Office", "type": "official/primary contextual authority", "relevance": "U.S. Copyright Office directly frames the domain question in Who Created the Value—and Who Gets It?; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by U.S. Copyright Office. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "U.S. Copyright Office provides bounded context for Build 084; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Created the Value—and Who Gets It? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 084 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Created the Value—and Who Gets It? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 084: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "U.S. Copyright Office provides bounded context for Build 084; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/084/build-084-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 084, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "U.S. Copyright Office provides bounded context for Build 084; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Created the Value—and Who Gets It? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 084 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Created the Value—and Who Gets It? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 084: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Who Created the Value—and Who Gets It? fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “U.S. Copyright Office provides bounded context for Build 084; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 084, 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." }, { "slide": 3, "stage": "System", "copy": [ "U.S. Copyright Office provides bounded context for Build 084; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Created the Value—and Who Gets It? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 084 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Created the Value—and Who Gets It? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 084: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Who Created the Value—and Who Gets It? mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 084, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "U.S. Copyright Office provides bounded context for Build 084; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Created the Value—and Who Gets It? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 084 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Created the Value—and Who Gets It? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 084: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. Copyright Office” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Authorship and rights context; not proof of contribution or allocation", "accessibility": "Slide 4 alt text must identify Build 084, 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.copyright.gov/what-is-copyright/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "U.S. Copyright Office provides bounded context for Build 084; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Created the Value—and Who Gets It? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 084 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Created the Value—and Who Gets It? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 084: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 084 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 084, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 084, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "U.S. Copyright Office provides bounded context for Build 084; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Created the Value—and Who Gets It? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 084 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Created the Value—and Who Gets It? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 084: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Who Created the Value—and Who Gets It? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 084, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "U.S. Copyright Office provides bounded context for Build 084; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Created the Value—and Who Gets It? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Copyright Office frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 084 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Created the Value—and Who Gets It? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 084: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 084: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 084, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 084, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "085", "title": "Who Is Shaping This Decision?", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/085/build-085-linkedin-poster.png", "altText": "Build 085, Who Is Shaping This Decision?: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Federal Register notice-and-comment process", "type": "official/primary contextual authority", "relevance": "Federal Register notice-and-comment process directly frames the domain question in Who Is Shaping This Decision?; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Office of the Federal Register. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Federal Register notice-and-comment process provides bounded context for Build 085; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Is Shaping This Decision? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register notice-and-comment process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 085 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Is Shaping This Decision? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 085: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Federal Register notice-and-comment process provides bounded context for Build 085; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/085/build-085-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 085, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "Federal Register notice-and-comment process provides bounded context for Build 085; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Is Shaping This Decision? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register notice-and-comment process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 085 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Is Shaping This Decision? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 085: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Who Is Shaping This Decision? fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Federal Register notice-and-comment process provides bounded context for Build 085; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 085, 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." }, { "slide": 3, "stage": "System", "copy": [ "Federal Register notice-and-comment process provides bounded context for Build 085; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Is Shaping This Decision? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register notice-and-comment process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 085 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Is Shaping This Decision? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 085: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Who Is Shaping This Decision? mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 085, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Federal Register notice-and-comment process provides bounded context for Build 085; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Is Shaping This Decision? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register notice-and-comment process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 085 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Is Shaping This Decision? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 085: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: Federal Register notice-and-comment process frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Federal Register notice-and-comment process” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Participation context; not proof of influence or representation", "accessibility": "Slide 4 alt text must identify Build 085, 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.federalregister.gov/reader-aids/the-federal-register/the-rulemaking-process; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Federal Register notice-and-comment process provides bounded context for Build 085; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Is Shaping This Decision? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register notice-and-comment process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 085 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Is Shaping This Decision? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 085: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 085 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 085, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 085, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Federal Register notice-and-comment process provides bounded context for Build 085; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Is Shaping This Decision? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register notice-and-comment process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 085 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Is Shaping This Decision? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 085: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Who Is Shaping This Decision? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 085, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Federal Register notice-and-comment process provides bounded context for Build 085; the proposition, scenario, and prototype are RN synthesis.", "The problem: Who Is Shaping This Decision? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register notice-and-comment process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 085 prototype. Show the interaction or decision path, not an invented result.", "Implication: Who Is Shaping This Decision? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 085: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 085: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 085, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 085, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "086", "title": "Use the Post as a Prototype", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/086/build-086-linkedin-poster.png", "altText": "Build 086, Use the Post as a Prototype: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "U.S. Web Design System", "type": "official/primary contextual authority", "relevance": "U.S. Web Design System directly frames the domain question in Use the Post as a Prototype; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by General Services Administration. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "U.S. Web Design System provides bounded context for Build 086; the proposition, scenario, and prototype are RN synthesis.", "The problem: Use the Post as a Prototype fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 086 prototype. Show the interaction or decision path, not an invented result.", "Implication: Use the Post as a Prototype can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 086: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "U.S. Web Design System provides bounded context for Build 086; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/086/build-086-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 086, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "U.S. Web Design System provides bounded context for Build 086; the proposition, scenario, and prototype are RN synthesis.", "The problem: Use the Post as a Prototype fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 086 prototype. Show the interaction or decision path, not an invented result.", "Implication: Use the Post as a Prototype can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 086: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Use the Post as a Prototype fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “U.S. Web Design System provides bounded context for Build 086; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 086, 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." }, { "slide": 3, "stage": "System", "copy": [ "U.S. Web Design System provides bounded context for Build 086; the proposition, scenario, and prototype are RN synthesis.", "The problem: Use the Post as a Prototype fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 086 prototype. Show the interaction or decision path, not an invented result.", "Implication: Use the Post as a Prototype can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 086: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Use the Post as a Prototype mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 086, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "U.S. Web Design System provides bounded context for Build 086; the proposition, scenario, and prototype are RN synthesis.", "The problem: Use the Post as a Prototype fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 086 prototype. Show the interaction or decision path, not an invented result.", "Implication: Use the Post as a Prototype can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 086: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: U.S. Web Design System frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “U.S. Web Design System” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Prototype and public-service design context; not performance evidence", "accessibility": "Slide 4 alt text must identify Build 086, 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://designsystem.digital.gov/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "U.S. Web Design System provides bounded context for Build 086; the proposition, scenario, and prototype are RN synthesis.", "The problem: Use the Post as a Prototype fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 086 prototype. Show the interaction or decision path, not an invented result.", "Implication: Use the Post as a Prototype can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 086: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 086 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 086, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 086, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "U.S. Web Design System provides bounded context for Build 086; the proposition, scenario, and prototype are RN synthesis.", "The problem: Use the Post as a Prototype fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 086 prototype. Show the interaction or decision path, not an invented result.", "Implication: Use the Post as a Prototype can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 086: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Use the Post as a Prototype can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 086, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "U.S. Web Design System provides bounded context for Build 086; the proposition, scenario, and prototype are RN synthesis.", "The problem: Use the Post as a Prototype fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: U.S. Web Design System frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 086 prototype. Show the interaction or decision path, not an invented result.", "Implication: Use the Post as a Prototype can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 086: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 086: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 086, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 086, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "087", "title": "Build Your Own Media System", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/087/build-087-linkedin-poster.png", "altText": "Build 087, Build Your Own Media System: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Digital.gov content guide", "type": "official/primary contextual authority", "relevance": "Digital.gov content guide directly frames the domain question in Build Your Own Media System; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by General Services Administration. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Digital.gov content guide provides bounded context for Build 087; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build Your Own Media System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Digital.gov content guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 087 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build Your Own Media System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 087: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Digital.gov content guide provides bounded context for Build 087; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/087/build-087-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 087, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "Digital.gov content guide provides bounded context for Build 087; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build Your Own Media System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Digital.gov content guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 087 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build Your Own Media System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 087: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Build Your Own Media System fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Digital.gov content guide provides bounded context for Build 087; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 087, 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." }, { "slide": 3, "stage": "System", "copy": [ "Digital.gov content guide provides bounded context for Build 087; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build Your Own Media System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Digital.gov content guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 087 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build Your Own Media System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 087: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Build Your Own Media System mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 087, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Digital.gov content guide provides bounded context for Build 087; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build Your Own Media System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Digital.gov content guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 087 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build Your Own Media System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 087: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: Digital.gov content guide frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Digital.gov content guide” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Media-system context; RN workflow remains a design proposition", "accessibility": "Slide 4 alt text must identify Build 087, 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://digital.gov/resources/; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Digital.gov content guide provides bounded context for Build 087; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build Your Own Media System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Digital.gov content guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 087 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build Your Own Media System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 087: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 087 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 087, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 087, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Digital.gov content guide provides bounded context for Build 087; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build Your Own Media System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Digital.gov content guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 087 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build Your Own Media System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 087: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Build Your Own Media System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 087, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Digital.gov content guide provides bounded context for Build 087; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build Your Own Media System fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Digital.gov content guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 087 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build Your Own Media System can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 087: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 087: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 087, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 087, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "088", "title": "Your Network Is Not a Contact List", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/088/build-088-linkedin-poster.png", "altText": "Build 088, Your Network Is Not a Contact List: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "LinkedIn data portability context", "type": "official/primary contextual authority", "relevance": "LinkedIn data portability context directly frames the domain question in Your Network Is Not a Contact List; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Federal Trade Commission. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "LinkedIn data portability context provides bounded context for Build 088; the proposition, scenario, and prototype are RN synthesis.", "The problem: Your Network Is Not a Contact List fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: LinkedIn data portability context frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 088 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Network Is Not a Contact List can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 088: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "LinkedIn data portability context provides bounded context for Build 088; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/088/build-088-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 088, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "LinkedIn data portability context provides bounded context for Build 088; the proposition, scenario, and prototype are RN synthesis.", "The problem: Your Network Is Not a Contact List fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: LinkedIn data portability context frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 088 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Network Is Not a Contact List can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 088: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Your Network Is Not a Contact List fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “LinkedIn data portability context provides bounded context for Build 088; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 088, 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." }, { "slide": 3, "stage": "System", "copy": [ "LinkedIn data portability context provides bounded context for Build 088; the proposition, scenario, and prototype are RN synthesis.", "The problem: Your Network Is Not a Contact List fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: LinkedIn data portability context frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 088 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Network Is Not a Contact List can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 088: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Your Network Is Not a Contact List mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 088, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "LinkedIn data portability context provides bounded context for Build 088; the proposition, scenario, and prototype are RN synthesis.", "The problem: Your Network Is Not a Contact List fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: LinkedIn data portability context frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 088 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Network Is Not a Contact List can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 088: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: LinkedIn data portability context frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “LinkedIn data portability context” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Privacy context; no platform endorsement or network-value proof", "accessibility": "Slide 4 alt text must identify Build 088, 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://consumer.ftc.gov/articles/how-protect-your-privacy-apps; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "LinkedIn data portability context provides bounded context for Build 088; the proposition, scenario, and prototype are RN synthesis.", "The problem: Your Network Is Not a Contact List fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: LinkedIn data portability context frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 088 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Network Is Not a Contact List can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 088: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 088 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 088, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 088, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "LinkedIn data portability context provides bounded context for Build 088; the proposition, scenario, and prototype are RN synthesis.", "The problem: Your Network Is Not a Contact List fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: LinkedIn data portability context frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 088 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Network Is Not a Contact List can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 088: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Your Network Is Not a Contact List can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 088, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "LinkedIn data portability context provides bounded context for Build 088; the proposition, scenario, and prototype are RN synthesis.", "The problem: Your Network Is Not a Contact List fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: LinkedIn data portability context frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 088 prototype. Show the interaction or decision path, not an invented result.", "Implication: Your Network Is Not a Contact List can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 088: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 088: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 088, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 088, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "089", "title": "Stop Being the Only Database in Your Company", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/089/build-089-linkedin-poster.png", "altText": "Build 089, Stop Being the Only Database in Your Company: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST data integrity guidance", "type": "official/primary contextual authority", "relevance": "NIST data integrity guidance directly frames the domain question in Stop Being the Only Database in Your Company; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Institute of Standards and Technology. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "NIST data integrity guidance provides bounded context for Build 089; the proposition, scenario, and prototype are RN synthesis.", "The problem: Stop Being the Only Database in Your Company fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 089 prototype. Show the interaction or decision path, not an invented result.", "Implication: Stop Being the Only Database in Your Company can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 089: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "NIST data integrity guidance provides bounded context for Build 089; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/089/build-089-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 089, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "NIST data integrity guidance provides bounded context for Build 089; the proposition, scenario, and prototype are RN synthesis.", "The problem: Stop Being the Only Database in Your Company fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 089 prototype. Show the interaction or decision path, not an invented result.", "Implication: Stop Being the Only Database in Your Company can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 089: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Stop Being the Only Database in Your Company fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “NIST data integrity guidance provides bounded context for Build 089; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 089, 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." }, { "slide": 3, "stage": "System", "copy": [ "NIST data integrity guidance provides bounded context for Build 089; the proposition, scenario, and prototype are RN synthesis.", "The problem: Stop Being the Only Database in Your Company fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 089 prototype. Show the interaction or decision path, not an invented result.", "Implication: Stop Being the Only Database in Your Company can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 089: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Stop Being the Only Database in Your Company mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 089, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "NIST data integrity guidance provides bounded context for Build 089; the proposition, scenario, and prototype are RN synthesis.", "The problem: Stop Being the Only Database in Your Company fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 089 prototype. Show the interaction or decision path, not an invented result.", "Implication: Stop Being the Only Database in Your Company can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 089: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST data integrity guidance” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Data-integrity context; not proof of organizational outcomes", "accessibility": "Slide 4 alt text must identify Build 089, 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://csrc.nist.gov/publications/detail/sp/1800-25/final; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "NIST data integrity guidance provides bounded context for Build 089; the proposition, scenario, and prototype are RN synthesis.", "The problem: Stop Being the Only Database in Your Company fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 089 prototype. Show the interaction or decision path, not an invented result.", "Implication: Stop Being the Only Database in Your Company can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 089: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 089 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 089, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 089, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "NIST data integrity guidance provides bounded context for Build 089; the proposition, scenario, and prototype are RN synthesis.", "The problem: Stop Being the Only Database in Your Company fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 089 prototype. Show the interaction or decision path, not an invented result.", "Implication: Stop Being the Only Database in Your Company can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 089: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Stop Being the Only Database in Your Company can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 089, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "NIST data integrity guidance provides bounded context for Build 089; the proposition, scenario, and prototype are RN synthesis.", "The problem: Stop Being the Only Database in Your Company fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 089 prototype. Show the interaction or decision path, not an invented result.", "Implication: Stop Being the Only Database in Your Company can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 089: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 089: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 089, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 089, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "090", "title": "Build a Research Team of AI Agents That Can Show Their Work", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/090/build-090-linkedin-poster.png", "altText": "Build 090, Build a Research Team of AI Agents That Can Show Their Work: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST AI Risk Management Framework", "type": "official/primary contextual authority", "relevance": "NIST AI Risk Management Framework directly frames the domain question in Build a Research Team of AI Agents That Can Show Their Work; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Institute of Standards and Technology. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 090; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build a Research Team of AI Agents That Can Show Their Work fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 090 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build a Research Team of AI Agents That Can Show Their Work can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 090: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "NIST AI Risk Management Framework provides bounded context for Build 090; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/090/build-090-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 090, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 090; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build a Research Team of AI Agents That Can Show Their Work fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 090 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build a Research Team of AI Agents That Can Show Their Work can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 090: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Build a Research Team of AI Agents That Can Show Their Work fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “NIST AI Risk Management Framework provides bounded context for Build 090; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 090, 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." }, { "slide": 3, "stage": "System", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 090; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build a Research Team of AI Agents That Can Show Their Work fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 090 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build a Research Team of AI Agents That Can Show Their Work can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 090: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Build a Research Team of AI Agents That Can Show Their Work mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 090, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 090; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build a Research Team of AI Agents That Can Show Their Work fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 090 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build a Research Team of AI Agents That Can Show Their Work can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 090: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST AI Risk Management Framework” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Traceable AI-risk context; agent team remains RN prototype", "accessibility": "Slide 4 alt text must identify Build 090, 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.nist.gov/itl/ai-risk-management-framework; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 090; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build a Research Team of AI Agents That Can Show Their Work fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 090 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build a Research Team of AI Agents That Can Show Their Work can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 090: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 090 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 090, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 090, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 090; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build a Research Team of AI Agents That Can Show Their Work fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 090 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build a Research Team of AI Agents That Can Show Their Work can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 090: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Build a Research Team of AI Agents That Can Show Their Work can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 090, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 090; the proposition, scenario, and prototype are RN synthesis.", "The problem: Build a Research Team of AI Agents That Can Show Their Work fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 090 prototype. Show the interaction or decision path, not an invented result.", "Implication: Build a Research Team of AI Agents That Can Show Their Work can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 090: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 090: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 090, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 090, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "091", "title": "What Is This AI Allowed to Remember?", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/091/build-091-linkedin-poster.png", "altText": "Build 091, What Is This AI Allowed to Remember?: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST Privacy Framework", "type": "official/primary contextual authority", "relevance": "NIST Privacy Framework directly frames the domain question in What Is This AI Allowed to Remember?; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Institute of Standards and Technology. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "NIST Privacy Framework provides bounded context for Build 091; the proposition, scenario, and prototype are RN synthesis.", "The problem: What Is This AI Allowed to Remember? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 091 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Is This AI Allowed to Remember? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 091: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "NIST Privacy Framework provides bounded context for Build 091; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/091/build-091-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 091, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "NIST Privacy Framework provides bounded context for Build 091; the proposition, scenario, and prototype are RN synthesis.", "The problem: What Is This AI Allowed to Remember? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 091 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Is This AI Allowed to Remember? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 091: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: What Is This AI Allowed to Remember? fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “NIST Privacy Framework provides bounded context for Build 091; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 091, 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." }, { "slide": 3, "stage": "System", "copy": [ "NIST Privacy Framework provides bounded context for Build 091; the proposition, scenario, and prototype are RN synthesis.", "The problem: What Is This AI Allowed to Remember? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 091 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Is This AI Allowed to Remember? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 091: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the What Is This AI Allowed to Remember? mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 091, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "NIST Privacy Framework provides bounded context for Build 091; the proposition, scenario, and prototype are RN synthesis.", "The problem: What Is This AI Allowed to Remember? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 091 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Is This AI Allowed to Remember? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 091: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST Privacy Framework” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Privacy-risk context; not proof of memory safety", "accessibility": "Slide 4 alt text must identify Build 091, 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.nist.gov/privacy-framework; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "NIST Privacy Framework provides bounded context for Build 091; the proposition, scenario, and prototype are RN synthesis.", "The problem: What Is This AI Allowed to Remember? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 091 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Is This AI Allowed to Remember? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 091: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 091 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 091, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 091, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "NIST Privacy Framework provides bounded context for Build 091; the proposition, scenario, and prototype are RN synthesis.", "The problem: What Is This AI Allowed to Remember? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 091 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Is This AI Allowed to Remember? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 091: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: What Is This AI Allowed to Remember? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 091, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "NIST Privacy Framework provides bounded context for Build 091; the proposition, scenario, and prototype are RN synthesis.", "The problem: What Is This AI Allowed to Remember? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 091 prototype. Show the interaction or decision path, not an invented result.", "Implication: What Is This AI Allowed to Remember? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 091: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 091: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 091, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 091, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "092", "title": "Rehearse Work Across People, AI and Software", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/092/build-092-linkedin-poster.png", "altText": "Build 092, Rehearse Work Across People, AI and Software: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST AI Risk Management Framework", "type": "official/primary contextual authority", "relevance": "NIST AI Risk Management Framework directly frames the domain question in Rehearse Work Across People, AI and Software; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Institute of Standards and Technology. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 092; the proposition, scenario, and prototype are RN synthesis.", "The problem: Rehearse Work Across People, AI and Software fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 092 prototype. Show the interaction or decision path, not an invented result.", "Implication: Rehearse Work Across People, AI and Software can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 092: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "NIST AI Risk Management Framework provides bounded context for Build 092; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/092/build-092-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 092, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 092; the proposition, scenario, and prototype are RN synthesis.", "The problem: Rehearse Work Across People, AI and Software fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 092 prototype. Show the interaction or decision path, not an invented result.", "Implication: Rehearse Work Across People, AI and Software can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 092: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Rehearse Work Across People, AI and Software fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “NIST AI Risk Management Framework provides bounded context for Build 092; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 092, 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." }, { "slide": 3, "stage": "System", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 092; the proposition, scenario, and prototype are RN synthesis.", "The problem: Rehearse Work Across People, AI and Software fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 092 prototype. Show the interaction or decision path, not an invented result.", "Implication: Rehearse Work Across People, AI and Software can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 092: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Rehearse Work Across People, AI and Software mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 092, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 092; the proposition, scenario, and prototype are RN synthesis.", "The problem: Rehearse Work Across People, AI and Software fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 092 prototype. Show the interaction or decision path, not an invented result.", "Implication: Rehearse Work Across People, AI and Software can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 092: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST AI Risk Management Framework” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Human-AI governance context; workflow is synthetic rehearsal", "accessibility": "Slide 4 alt text must identify Build 092, 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.nist.gov/itl/ai-risk-management-framework; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 092; the proposition, scenario, and prototype are RN synthesis.", "The problem: Rehearse Work Across People, AI and Software fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 092 prototype. Show the interaction or decision path, not an invented result.", "Implication: Rehearse Work Across People, AI and Software can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 092: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 092 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 092, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 092, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 092; the proposition, scenario, and prototype are RN synthesis.", "The problem: Rehearse Work Across People, AI and Software fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 092 prototype. Show the interaction or decision path, not an invented result.", "Implication: Rehearse Work Across People, AI and Software can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 092: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Rehearse Work Across People, AI and Software can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 092, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "NIST AI Risk Management Framework provides bounded context for Build 092; the proposition, scenario, and prototype are RN synthesis.", "The problem: Rehearse Work Across People, AI and Software fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST AI Risk Management Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 092 prototype. Show the interaction or decision path, not an invented result.", "Implication: Rehearse Work Across People, AI and Software can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 092: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 092: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 092, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 092, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "093", "title": "Fictional Regulated-Workflow Rehearsal", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/093/build-093-linkedin-poster.png", "altText": "Build 093, Fictional Regulated-Workflow Rehearsal: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "FDA Quality Systems guidance", "type": "official/primary contextual authority", "relevance": "FDA Quality Systems guidance directly frames the domain question in Fictional Regulated-Workflow Rehearsal; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by U.S. Food and Drug Administration. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "FDA Quality Systems guidance provides bounded context for Build 093; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Regulated-Workflow Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA Quality Systems guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 093 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Regulated-Workflow Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 093: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "FDA Quality Systems guidance provides bounded context for Build 093; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/093/build-093-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 093, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "FDA Quality Systems guidance provides bounded context for Build 093; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Regulated-Workflow Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA Quality Systems guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 093 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Regulated-Workflow Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 093: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Fictional Regulated-Workflow Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “FDA Quality Systems guidance provides bounded context for Build 093; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 093, 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." }, { "slide": 3, "stage": "System", "copy": [ "FDA Quality Systems guidance provides bounded context for Build 093; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Regulated-Workflow Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA Quality Systems guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 093 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Regulated-Workflow Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 093: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Fictional Regulated-Workflow Rehearsal mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 093, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "FDA Quality Systems guidance provides bounded context for Build 093; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Regulated-Workflow Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA Quality Systems guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 093 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Regulated-Workflow Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 093: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: FDA Quality Systems guidance frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “FDA Quality Systems guidance” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Regulated-workflow context only; scenario remains fictional", "accessibility": "Slide 4 alt text must identify Build 093, 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.fda.gov/regulatory-information/search-fda-guidance-documents/quality-systems-approach-pharmaceutical-current-good-manufacturing-practice-regulations; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "FDA Quality Systems guidance provides bounded context for Build 093; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Regulated-Workflow Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA Quality Systems guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 093 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Regulated-Workflow Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 093: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 093 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 093, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 093, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "FDA Quality Systems guidance provides bounded context for Build 093; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Regulated-Workflow Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA Quality Systems guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 093 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Regulated-Workflow Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 093: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Fictional Regulated-Workflow Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 093, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "FDA Quality Systems guidance provides bounded context for Build 093; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Regulated-Workflow Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA Quality Systems guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 093 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Regulated-Workflow Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 093: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 093: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 093, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 093, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "094", "title": "Inspect a Fictional Evidence Chain", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/094/build-094-linkedin-poster.png", "altText": "Build 094, Inspect a Fictional Evidence Chain: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST data integrity guidance", "type": "official/primary contextual authority", "relevance": "NIST data integrity guidance directly frames the domain question in Inspect a Fictional Evidence Chain; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Institute of Standards and Technology. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "NIST data integrity guidance provides bounded context for Build 094; the proposition, scenario, and prototype are RN synthesis.", "The problem: Inspect a Fictional Evidence Chain fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 094 prototype. Show the interaction or decision path, not an invented result.", "Implication: Inspect a Fictional Evidence Chain can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 094: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "NIST data integrity guidance provides bounded context for Build 094; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/094/build-094-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 094, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "NIST data integrity guidance provides bounded context for Build 094; the proposition, scenario, and prototype are RN synthesis.", "The problem: Inspect a Fictional Evidence Chain fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 094 prototype. Show the interaction or decision path, not an invented result.", "Implication: Inspect a Fictional Evidence Chain can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 094: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Inspect a Fictional Evidence Chain fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “NIST data integrity guidance provides bounded context for Build 094; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 094, 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." }, { "slide": 3, "stage": "System", "copy": [ "NIST data integrity guidance provides bounded context for Build 094; the proposition, scenario, and prototype are RN synthesis.", "The problem: Inspect a Fictional Evidence Chain fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 094 prototype. Show the interaction or decision path, not an invented result.", "Implication: Inspect a Fictional Evidence Chain can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 094: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Inspect a Fictional Evidence Chain mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 094, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "NIST data integrity guidance provides bounded context for Build 094; the proposition, scenario, and prototype are RN synthesis.", "The problem: Inspect a Fictional Evidence Chain fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 094 prototype. Show the interaction or decision path, not an invented result.", "Implication: Inspect a Fictional Evidence Chain can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 094: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST data integrity guidance” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Integrity/provenance context; evidence chain remains fictional", "accessibility": "Slide 4 alt text must identify Build 094, 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://csrc.nist.gov/publications/detail/sp/1800-25/final; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "NIST data integrity guidance provides bounded context for Build 094; the proposition, scenario, and prototype are RN synthesis.", "The problem: Inspect a Fictional Evidence Chain fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 094 prototype. Show the interaction or decision path, not an invented result.", "Implication: Inspect a Fictional Evidence Chain can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 094: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 094 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 094, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 094, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "NIST data integrity guidance provides bounded context for Build 094; the proposition, scenario, and prototype are RN synthesis.", "The problem: Inspect a Fictional Evidence Chain fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 094 prototype. Show the interaction or decision path, not an invented result.", "Implication: Inspect a Fictional Evidence Chain can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 094: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Inspect a Fictional Evidence Chain can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 094, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "NIST data integrity guidance provides bounded context for Build 094; the proposition, scenario, and prototype are RN synthesis.", "The problem: Inspect a Fictional Evidence Chain fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST data integrity guidance frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 094 prototype. Show the interaction or decision path, not an invented result.", "Implication: Inspect a Fictional Evidence Chain can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 094: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 094: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 094, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 094, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "095", "title": "Institutional Conditions Observatory", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/095/build-095-linkedin-poster.png", "altText": "Build 095, Institutional Conditions Observatory: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "Federal Register official document system", "type": "official/primary contextual authority", "relevance": "Federal Register official document system directly frames the domain question in Institutional Conditions Observatory; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Office of the Federal Register. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "Federal Register official document system provides bounded context for Build 095; the proposition, scenario, and prototype are RN synthesis.", "The problem: Institutional Conditions Observatory fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register official document system frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 095 prototype. Show the interaction or decision path, not an invented result.", "Implication: Institutional Conditions Observatory can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 095: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Federal Register official document system provides bounded context for Build 095; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/095/build-095-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 095, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "Federal Register official document system provides bounded context for Build 095; the proposition, scenario, and prototype are RN synthesis.", "The problem: Institutional Conditions Observatory fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register official document system frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 095 prototype. Show the interaction or decision path, not an invented result.", "Implication: Institutional Conditions Observatory can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 095: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Institutional Conditions Observatory fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “Federal Register official document system provides bounded context for Build 095; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 095, 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." }, { "slide": 3, "stage": "System", "copy": [ "Federal Register official document system provides bounded context for Build 095; the proposition, scenario, and prototype are RN synthesis.", "The problem: Institutional Conditions Observatory fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register official document system frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 095 prototype. Show the interaction or decision path, not an invented result.", "Implication: Institutional Conditions Observatory can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 095: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Institutional Conditions Observatory mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 095, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "Federal Register official document system provides bounded context for Build 095; the proposition, scenario, and prototype are RN synthesis.", "The problem: Institutional Conditions Observatory fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register official document system frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 095 prototype. Show the interaction or decision path, not an invented result.", "Implication: Institutional Conditions Observatory can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 095: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: Federal Register official document system frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “Federal Register official document system” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Institutional-condition context; observatory is RN synthesis", "accessibility": "Slide 4 alt text must identify Build 095, 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.federalregister.gov/reader-aids/understanding-the-federal-register; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "Federal Register official document system provides bounded context for Build 095; the proposition, scenario, and prototype are RN synthesis.", "The problem: Institutional Conditions Observatory fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register official document system frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 095 prototype. Show the interaction or decision path, not an invented result.", "Implication: Institutional Conditions Observatory can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 095: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 095 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 095, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 095, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "Federal Register official document system provides bounded context for Build 095; the proposition, scenario, and prototype are RN synthesis.", "The problem: Institutional Conditions Observatory fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register official document system frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 095 prototype. Show the interaction or decision path, not an invented result.", "Implication: Institutional Conditions Observatory can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 095: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Institutional Conditions Observatory can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 095, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "Federal Register official document system provides bounded context for Build 095; the proposition, scenario, and prototype are RN synthesis.", "The problem: Institutional Conditions Observatory fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: Federal Register official document system frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 095 prototype. Show the interaction or decision path, not an invented result.", "Implication: Institutional Conditions Observatory can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 095: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 095: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 095, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 095, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "096", "title": "Learn From Cannabis Experience Without Reducing People to Labels", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/096/build-096-linkedin-poster.png", "altText": "Build 096, Learn From Cannabis Experience Without Reducing People to Labels: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "CDC Principles of Community Engagement", "type": "official/primary contextual authority", "relevance": "CDC Principles of Community Engagement directly frames the domain question in Learn From Cannabis Experience Without Reducing People to Labels; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Centers for Disease Control and Prevention. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "CDC Principles of Community Engagement provides bounded context for Build 096; the proposition, scenario, and prototype are RN synthesis.", "The problem: Learn From Cannabis Experience Without Reducing People to Labels fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Principles of Community Engagement frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 096 prototype. Show the interaction or decision path, not an invented result.", "Implication: Learn From Cannabis Experience Without Reducing People to Labels can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 096: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "CDC Principles of Community Engagement provides bounded context for Build 096; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/096/build-096-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 096, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "CDC Principles of Community Engagement provides bounded context for Build 096; the proposition, scenario, and prototype are RN synthesis.", "The problem: Learn From Cannabis Experience Without Reducing People to Labels fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Principles of Community Engagement frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 096 prototype. Show the interaction or decision path, not an invented result.", "Implication: Learn From Cannabis Experience Without Reducing People to Labels can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 096: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Learn From Cannabis Experience Without Reducing People to Labels fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “CDC Principles of Community Engagement provides bounded context for Build 096; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 096, 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." }, { "slide": 3, "stage": "System", "copy": [ "CDC Principles of Community Engagement provides bounded context for Build 096; the proposition, scenario, and prototype are RN synthesis.", "The problem: Learn From Cannabis Experience Without Reducing People to Labels fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Principles of Community Engagement frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 096 prototype. Show the interaction or decision path, not an invented result.", "Implication: Learn From Cannabis Experience Without Reducing People to Labels can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 096: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Learn From Cannabis Experience Without Reducing People to Labels mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 096, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "CDC Principles of Community Engagement provides bounded context for Build 096; the proposition, scenario, and prototype are RN synthesis.", "The problem: Learn From Cannabis Experience Without Reducing People to Labels fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Principles of Community Engagement frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 096 prototype. Show the interaction or decision path, not an invented result.", "Implication: Learn From Cannabis Experience Without Reducing People to Labels can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 096: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: CDC Principles of Community Engagement frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “CDC Principles of Community Engagement” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Engagement context; no lived-experience representation or community authority", "accessibility": "Slide 4 alt text must identify Build 096, 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.atsdr.cdc.gov/community-engagement-playbook/php/about/index.html; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "CDC Principles of Community Engagement provides bounded context for Build 096; the proposition, scenario, and prototype are RN synthesis.", "The problem: Learn From Cannabis Experience Without Reducing People to Labels fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Principles of Community Engagement frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 096 prototype. Show the interaction or decision path, not an invented result.", "Implication: Learn From Cannabis Experience Without Reducing People to Labels can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 096: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 096 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 096, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 096, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "CDC Principles of Community Engagement provides bounded context for Build 096; the proposition, scenario, and prototype are RN synthesis.", "The problem: Learn From Cannabis Experience Without Reducing People to Labels fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Principles of Community Engagement frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 096 prototype. Show the interaction or decision path, not an invented result.", "Implication: Learn From Cannabis Experience Without Reducing People to Labels can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 096: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Learn From Cannabis Experience Without Reducing People to Labels can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 096, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "CDC Principles of Community Engagement provides bounded context for Build 096; the proposition, scenario, and prototype are RN synthesis.", "The problem: Learn From Cannabis Experience Without Reducing People to Labels fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: CDC Principles of Community Engagement frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 096 prototype. Show the interaction or decision path, not an invented result.", "Implication: Learn From Cannabis Experience Without Reducing People to Labels can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 096: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 096: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 096, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 096, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "097", "title": "Can Personalization Respect the Off Switch?", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/097/build-097-linkedin-poster.png", "altText": "Build 097, Can Personalization Respect the Off Switch?: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST Privacy Framework", "type": "official/primary contextual authority", "relevance": "NIST Privacy Framework directly frames the domain question in Can Personalization Respect the Off Switch?; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Institute of Standards and Technology. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "NIST Privacy Framework provides bounded context for Build 097; the proposition, scenario, and prototype are RN synthesis.", "The problem: Can Personalization Respect the Off Switch? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 097 prototype. Show the interaction or decision path, not an invented result.", "Implication: Can Personalization Respect the Off Switch? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 097: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "NIST Privacy Framework provides bounded context for Build 097; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/097/build-097-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 097, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "NIST Privacy Framework provides bounded context for Build 097; the proposition, scenario, and prototype are RN synthesis.", "The problem: Can Personalization Respect the Off Switch? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 097 prototype. Show the interaction or decision path, not an invented result.", "Implication: Can Personalization Respect the Off Switch? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 097: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Can Personalization Respect the Off Switch? fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “NIST Privacy Framework provides bounded context for Build 097; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 097, 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." }, { "slide": 3, "stage": "System", "copy": [ "NIST Privacy Framework provides bounded context for Build 097; the proposition, scenario, and prototype are RN synthesis.", "The problem: Can Personalization Respect the Off Switch? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 097 prototype. Show the interaction or decision path, not an invented result.", "Implication: Can Personalization Respect the Off Switch? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 097: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Can Personalization Respect the Off Switch? mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 097, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "NIST Privacy Framework provides bounded context for Build 097; the proposition, scenario, and prototype are RN synthesis.", "The problem: Can Personalization Respect the Off Switch? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 097 prototype. Show the interaction or decision path, not an invented result.", "Implication: Can Personalization Respect the Off Switch? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 097: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST Privacy Framework” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Privacy-control context; not proof that personalization respects withdrawal", "accessibility": "Slide 4 alt text must identify Build 097, 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.nist.gov/privacy-framework; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "NIST Privacy Framework provides bounded context for Build 097; the proposition, scenario, and prototype are RN synthesis.", "The problem: Can Personalization Respect the Off Switch? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 097 prototype. Show the interaction or decision path, not an invented result.", "Implication: Can Personalization Respect the Off Switch? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 097: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 097 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 097, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 097, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "NIST Privacy Framework provides bounded context for Build 097; the proposition, scenario, and prototype are RN synthesis.", "The problem: Can Personalization Respect the Off Switch? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 097 prototype. Show the interaction or decision path, not an invented result.", "Implication: Can Personalization Respect the Off Switch? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 097: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Can Personalization Respect the Off Switch? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 097, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "NIST Privacy Framework provides bounded context for Build 097; the proposition, scenario, and prototype are RN synthesis.", "The problem: Can Personalization Respect the Off Switch? fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 097 prototype. Show the interaction or decision path, not an invented result.", "Implication: Can Personalization Respect the Off Switch? can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 097: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 097: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 097, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 097, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "098", "title": "Psychedelic Administrative Handoff Rehearsal", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/098/build-098-linkedin-poster.png", "altText": "Build 098, Psychedelic Administrative Handoff Rehearsal: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "FDA drug development process", "type": "official/primary contextual authority", "relevance": "FDA drug development process directly frames the domain question in Psychedelic Administrative Handoff Rehearsal; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by U.S. Food and Drug Administration. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "FDA drug development process provides bounded context for Build 098; the proposition, scenario, and prototype are RN synthesis.", "The problem: Psychedelic Administrative Handoff Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA drug development process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 098 prototype. Show the interaction or decision path, not an invented result.", "Implication: Psychedelic Administrative Handoff Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 098: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "FDA drug development process provides bounded context for Build 098; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/098/build-098-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 098, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "FDA drug development process provides bounded context for Build 098; the proposition, scenario, and prototype are RN synthesis.", "The problem: Psychedelic Administrative Handoff Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA drug development process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 098 prototype. Show the interaction or decision path, not an invented result.", "Implication: Psychedelic Administrative Handoff Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 098: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Psychedelic Administrative Handoff Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “FDA drug development process provides bounded context for Build 098; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 098, 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." }, { "slide": 3, "stage": "System", "copy": [ "FDA drug development process provides bounded context for Build 098; the proposition, scenario, and prototype are RN synthesis.", "The problem: Psychedelic Administrative Handoff Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA drug development process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 098 prototype. Show the interaction or decision path, not an invented result.", "Implication: Psychedelic Administrative Handoff Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 098: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Psychedelic Administrative Handoff Rehearsal mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 098, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "FDA drug development process provides bounded context for Build 098; the proposition, scenario, and prototype are RN synthesis.", "The problem: Psychedelic Administrative Handoff Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA drug development process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 098 prototype. Show the interaction or decision path, not an invented result.", "Implication: Psychedelic Administrative Handoff Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 098: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: FDA drug development process frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “FDA drug development process” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Administrative handoff context only; psychedelic scenario is fictional and nonclinical", "accessibility": "Slide 4 alt text must identify Build 098, 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.fda.gov/patients/drug-development-process/step-5-fda-post-market-drug-safety-monitoring; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "FDA drug development process provides bounded context for Build 098; the proposition, scenario, and prototype are RN synthesis.", "The problem: Psychedelic Administrative Handoff Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA drug development process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 098 prototype. Show the interaction or decision path, not an invented result.", "Implication: Psychedelic Administrative Handoff Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 098: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 098 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 098, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 098, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "FDA drug development process provides bounded context for Build 098; the proposition, scenario, and prototype are RN synthesis.", "The problem: Psychedelic Administrative Handoff Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA drug development process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 098 prototype. Show the interaction or decision path, not an invented result.", "Implication: Psychedelic Administrative Handoff Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 098: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Psychedelic Administrative Handoff Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 098, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "FDA drug development process provides bounded context for Build 098; the proposition, scenario, and prototype are RN synthesis.", "The problem: Psychedelic Administrative Handoff Rehearsal fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FDA drug development process frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 098 prototype. Show the interaction or decision path, not an invented result.", "Implication: Psychedelic Administrative Handoff Rehearsal can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 098: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 098: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 098, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 098, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "099", "title": "Fictional Archipelago Data Commons", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/099/build-099-linkedin-poster.png", "altText": "Build 099, Fictional Archipelago Data Commons: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "NIST Privacy Framework", "type": "official/primary contextual authority", "relevance": "NIST Privacy Framework directly frames the domain question in Fictional Archipelago Data Commons; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by National Institute of Standards and Technology. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "NIST Privacy Framework provides bounded context for Build 099; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Archipelago Data Commons fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 099 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Archipelago Data Commons can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 099: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "NIST Privacy Framework provides bounded context for Build 099; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/099/build-099-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 099, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "NIST Privacy Framework provides bounded context for Build 099; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Archipelago Data Commons fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 099 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Archipelago Data Commons can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 099: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Fictional Archipelago Data Commons fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “NIST Privacy Framework provides bounded context for Build 099; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 099, 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." }, { "slide": 3, "stage": "System", "copy": [ "NIST Privacy Framework provides bounded context for Build 099; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Archipelago Data Commons fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 099 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Archipelago Data Commons can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 099: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Fictional Archipelago Data Commons mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 099, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "NIST Privacy Framework provides bounded context for Build 099; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Archipelago Data Commons fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 099 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Archipelago Data Commons can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 099: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “NIST Privacy Framework” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Data-governance context; archipelago and commons are fictional", "accessibility": "Slide 4 alt text must identify Build 099, 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.nist.gov/privacy-framework; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "NIST Privacy Framework provides bounded context for Build 099; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Archipelago Data Commons fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 099 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Archipelago Data Commons can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 099: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 099 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 099, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 099, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "NIST Privacy Framework provides bounded context for Build 099; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Archipelago Data Commons fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 099 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Archipelago Data Commons can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 099: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Fictional Archipelago Data Commons can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 099, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "NIST Privacy Framework provides bounded context for Build 099; the proposition, scenario, and prototype are RN synthesis.", "The problem: Fictional Archipelago Data Commons fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: NIST Privacy Framework frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 099 prototype. Show the interaction or decision path, not an invented result.", "Implication: Fictional Archipelago Data Commons can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 099: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 099: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 099, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 099, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] }, { "buildId": "100", "title": "Island Resilience Scenario & Decision Room", "template": "4:5 RN Builds social cover", "status": "RN_OWNED", "coverMapping": { "assetUrl": "/media/builds/100/build-100-linkedin-poster.png", "altText": "Build 100, Island Resilience Scenario & Decision Room: creator-owned 4:5 typographic cover.", "credit": "© RN Collins · RN Builds", "sourceUrl": null, "rollbackAssetUrl": null }, "recognizableEntity": { "label": "FEMA Supply Chain Resilience Guide", "type": "official/primary contextual authority", "relevance": "FEMA Supply Chain Resilience Guide directly frames the domain question in Island Resilience Scenario & Decision Room; relevance is contextual, not promotional.", "authorizationBoundary": "No affiliation or endorsement by Federal Emergency Management Agency. Recognition does not authorize marks, screenshots, portraits, or trade dress." }, "slides": [ { "slide": 1, "stage": "Hook", "copy": [ "FEMA Supply Chain Resilience Guide provides bounded context for Build 100; the proposition, scenario, and prototype are RN synthesis.", "The problem: Island Resilience Scenario & Decision Room fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FEMA Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 100 prototype. Show the interaction or decision path, not an invented result.", "Implication: Island Resilience Scenario & Decision Room can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 100: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "FEMA Supply Chain Resilience Guide provides bounded context for Build 100; the proposition, scenario, and prototype are RN synthesis.", "visualGuidance": "Use the complete RN-owned cover at /media/builds/100/build-100-linkedin-poster.png. Do not crop text, credits, safe margins, or claim boundary.", "claimBoundary": "Build identity and RN proposition only; not documentary evidence or endorsement.", "accessibility": "Slide 1 alt text must identify Build 100, the hook function, essential visible text, and the information conveyed by the visual. Keep reading order headline → visual → boundary/credit.", "rights": "Creator-owned; no third-party visual used." }, { "slide": 2, "stage": "Problem", "copy": [ "FEMA Supply Chain Resilience Guide provides bounded context for Build 100; the proposition, scenario, and prototype are RN synthesis.", "The problem: Island Resilience Scenario & Decision Room fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FEMA Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 100 prototype. Show the interaction or decision path, not an invented result.", "Implication: Island Resilience Scenario & Decision Room can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 100: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The problem: Island Resilience Scenario & Decision Room fails when the underlying decision, audience, or evidence boundary is left implicit.", "visualGuidance": "RN-owned problem framing: isolate the tension behind “FEMA Supply Chain Resilience Guide provides bounded context for Build 100; the proposition, scenario, and prototype are RN synthesis.”. Use typography plus one simple contrast or decision fork; no stock people.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 2 alt text must identify Build 100, 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." }, { "slide": 3, "stage": "System", "copy": [ "FEMA Supply Chain Resilience Guide provides bounded context for Build 100; the proposition, scenario, and prototype are RN synthesis.", "The problem: Island Resilience Scenario & Decision Room fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FEMA Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 100 prototype. Show the interaction or decision path, not an invented result.", "Implication: Island Resilience Scenario & Decision Room can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 100: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "visualGuidance": "Show an RN-owned diagram or prototype view of the Island Resilience Scenario & Decision Room mechanism. Label inputs, decision/action, and output; do not depict outcomes not present in the build.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 3 alt text must identify Build 100, 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." }, { "slide": 4, "stage": "Evidence", "copy": [ "FEMA Supply Chain Resilience Guide provides bounded context for Build 100; the proposition, scenario, and prototype are RN synthesis.", "The problem: Island Resilience Scenario & Decision Room fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FEMA Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 100 prototype. Show the interaction or decision path, not an invented result.", "Implication: Island Resilience Scenario & Decision Room can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 100: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Evidence boundary: FEMA Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "visualGuidance": "Use an RN-owned evidence-boundary card. The recognizable entity “FEMA Supply Chain Resilience Guide” may be named as context only; do not use its marks, screenshots, portraits, or trade dress.", "claimBoundary": "Resilience-planning context; island scenario and decisions remain synthetic", "accessibility": "Slide 4 alt text must identify Build 100, 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.fema.gov/emergency-managers/risk-management/building-science/supply-chain-resilience-guide; no third-party visual authorized." }, { "slide": 5, "stage": "Demo", "copy": [ "FEMA Supply Chain Resilience Guide provides bounded context for Build 100; the proposition, scenario, and prototype are RN synthesis.", "The problem: Island Resilience Scenario & Decision Room fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FEMA Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 100 prototype. Show the interaction or decision path, not an invented result.", "Implication: Island Resilience Scenario & Decision Room can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 100: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Demo: walk through one bounded state change in the Build 100 prototype. Show the interaction or decision path, not an invented result.", "visualGuidance": "Use an authentic RN prototype/interface capture from Build 100, or a faithful RN-owned diagram if no stable interface view exists. Clearly label simulated, fictional, or illustrative states.", "claimBoundary": "Show only an observed prototype state; label simulation and fiction; do not imply deployment or outcome.", "accessibility": "Slide 5 alt text must identify Build 100, 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." }, { "slide": 6, "stage": "Implications", "copy": [ "FEMA Supply Chain Resilience Guide provides bounded context for Build 100; the proposition, scenario, and prototype are RN synthesis.", "The problem: Island Resilience Scenario & Decision Room fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FEMA Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 100 prototype. Show the interaction or decision path, not an invented result.", "Implication: Island Resilience Scenario & Decision Room can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 100: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Implication: Island Resilience Scenario & Decision Room can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "visualGuidance": "Use a two-column RN synthesis: what this build makes possible / what it does not establish. No universal, causal, safety, compliance, or effectiveness claim.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 6 alt text must identify Build 100, 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." }, { "slide": 7, "stage": "CTA + sources", "copy": [ "FEMA Supply Chain Resilience Guide provides bounded context for Build 100; the proposition, scenario, and prototype are RN synthesis.", "The problem: Island Resilience Scenario & Decision Room fails when the underlying decision, audience, or evidence boundary is left implicit.", "The system: make the mechanism inspectable—show what enters, what changes, who retains authority, and what leaves the system.", "Evidence boundary: FEMA Supply Chain Resilience Guide frames the domain; the proposition and prototype remain RN synthesis.", "Demo: walk through one bounded state change in the Build 100 prototype. Show the interaction or decision path, not an invented result.", "Implication: Island Resilience Scenario & Decision Room can make the relevant structure visible and discussable. It does not by itself prove performance, compliance, safety, effectiveness, causation, or endorsement.", "Explore Build 100: inspect the source boundary, motion argument, and interactive prototype." ], "headline": "Explore Build 100: inspect the source boundary, motion argument, and interactive prototype.", "visualGuidance": "Use a quiet RN-owned closing card with Build 100, the canonical dossier URL, CTA, source/credit line, and “RN synthesis · no endorsement” where an institution is named.", "claimBoundary": "RN synthesis only; avoid performance, compliance, safety, effectiveness, causal, testimonial, or endorsement claims.", "accessibility": "Slide 7 alt text must identify Build 100, 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." } ], "platformRepurposing": { "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.", "reelsTikTok": "Animate slides 1–6 as silent-first vertical beats; retain captions, visible source credit, and final CTA; do not imply motion footage is documentary.", "webNewsletter": "Use slide 1 as the preview and embed/link the dossier; do not detach the source-context image from its caption, credit, and limitation." }, "finalGates": [ "actual build content checked", "cover mapping intact", "recognizable hook fit checked", "rights/credit checked", "claim boundary checked", "alt text written", "mobile legibility checked", "links checked", "editorial approval recorded" ] } ] }