ZGZac Gibson
evidence atlas

Zac Gibson

Product Analyst×AI Product Builder×Author

I work in healthcare technology,
build digital products with AI, and write fiction.

Proof loop

  1. 01

    Start with
    a clear task

  2. 02

    Gather
    the evidence

  3. 03

    Check
    the decision

  4. 04

    Keep
    the record

AI / MEMORY & VERIFICATION

SLUICE

Better memory starts with evidence.

Brings back relevant context and checks the evidence before saving a new lesson. Explore how it handles a decision, including when it has to stop.

The operating rules

BOUNDOnly relevant context enters.PROVEDClaim and same-run evidence travel together.RECORDEDAllow, deny, or hold keeps its reason.

SLUICE / CONTROL CURRENTTRACE 01 / 05

CONTEXT BOUNDEVIDENCE CHECKEDREADY ON VIEW

working kernel 01 · memory promotion

Should this become standing context?

An assistant wants to keep a useful preference for future work.
  1. requestRemember this preference
  2. bounded contextConversation + current task
  3. evidenceNo exact source span attached
  4. policy gatePromotion needs source + proof ID
  5. receiptMemory unchanged; reason kept

WHYA plausible lesson is still refused when its origin cannot be inspected.

CONTROL BOUNDARYOne working kernel path and four illustrative transfer patterns—not live integrations or autonomous authority.

EXAMPLE RECEIPTDENYMemory unchanged; reason kept

One working kernel · four illustrative patterns · each example keeps its reason
See the recorded SLUICE showcase
SOURCE RECORD 01 / 02 / SLUICEThe refusal, in its own words
Inspect this capture (opens the original file when inspection is unavailable)
RECORDED / 24 SEP 2026

SLUICE — A claim stopped at the gate

A recorded image. Zoom in and scroll to read closely; closing returns you to the page.

SLUICE public showcase stating an unsupported dual-win marketing claim was refused
SLUICE public showcase stating an unsupported dual-win marketing claim was refused
Recorded frame24 SEP 2026
WHAT TO NOTICE

The public showcase refuses an unsupported smarter-model claim. Its terminal is receipt-backed theater, not evidence of enforcement across every caller.

Public showcase · receipt-backed theater · callable does not mean enforced
Source & recording details
Source page
sluice.zacgibson.work/
Displayed image
Recorded frame · 24 SEP 2026
Date label source
Supplied metadata

The detail and full record are separate saved images. Their dates are recorded independently.

IDENTITY / FICTIONAL HEALTH NETWORK

Northbridge
Horizon

IAM lab for a fictional health network.

Follow a proposed access change from source evidence to policy review and a human decision.

How the lab works →
SOURCE RECORD 01 / 03 / NORTHBRIDGE HORIZONTest access. Keep care moving.
Inspect this capture (opens the original file when inspection is unavailable)
RECORDED / 20 OCT 2026

Northbridge Horizon — Command Center

A recorded image. Zoom in and scroll to read closely; closing returns you to the page.

Northbridge Horizon v22 fictional healthcare lab: Test access changes. Keep care moving.
Northbridge Horizon v22 fictional healthcare lab: Test access changes. Keep care moving.
Full record20 OCT 2026
WHAT TO NOTICE

Start with a fictional hospital case: test an access change, find a smaller repair, and check whether needed care access recovers.

Recorded v22 · fictional teaching lab · no real access changes
Source & recording details
Source page
Northbridge Horizon v22 / command center
Displayed image
Full record · 20 OCT 2026
Date label source
Supplied metadata
Recorded edition
v22 source rendered locally at 2× density; fictional teaching lab
Source revision
7cb2ac26e4667e173e5446cd3cfa8f3872d2c451
See the five access checks
MechanismDescriptionIdentity path (sandbox)Path state
01Source evidencesynthetic HR and credential facts establish the casesource attachedmodeled
02Identity contextresolve role, assignment, facility, and scopecontext resolvedmodeled
03Candidate plancompile the proposed entitlement differenceplan preparedcandidate
04Policy reviewinspect eligibility, explicit deny, and conflictspolicy evaluatedreview
05Human ownershipbind accountable review to the exact planwriter heldbounded
CONTROL BOUNDARYFICTIONAL NETWORK · NO PHI · REVIEWABLE PATH
Inside the access workflow

THE COMMAND CENTER / FROM SOURCE TO AUTHORITY

Follow the access.
Find the boundary.

Explore a fictional health system. Inspect the candidate plan, the policy it must satisfy, and the evidence required before the next step.
Modeled identities
30,000
Application services
648
IAM domains
5
Production writes
0

Four roles. No autonomous authority.

Access Concierge
Structure the request.
Lifecycle Orchestrator
Prepare a candidate plan.
Governance Assurance
Explain policy and evidence.
Application Integration
Simulate the connector and read-back.

Deterministic agent simulations. These roles cannot authorize access or write directly to a target.

Explore the IAM laboratory (opens in a new tab)

CLINICIAN JOINER / ILLUSTRATED PATH

Authority has a stopping point.

Open any step to read the evidence.

  1. EstablishStart with source evidence.

    A synthetic HR event, credential evidence, and assignment establish the case. Missing evidence holds the request.

  2. ResolveResolve identity and scope.

    Access Concierge structures the request. Role, department, facility, and assignment determine its context.

  3. CompilePrepare the smallest valid plan.

    Lifecycle Orchestrator compiles a candidate entitlement difference. Preparing a plan does not grant access.

  4. ControlCheck policy before permission.

    Eligibility, explicit deny, least privilege, and separation of duties are evaluated. Governance Assurance explains the evidence.

  5. AccountBind review to the exact plan.

    A named human owner must review the candidate. A changed plan needs fresh review. This illustrated case stops here.

  6. ExecuteHold at the writer boundary.

    Application Integration previews the target operation. The laboratory has no production writer.

  7. ProveRequire independent read-back.

    The reference design compares target state with the approved plan and keeps the result. This simulation makes no external change.

CASE STOPS AT 05Awaiting accountable ownerStages 06–07 remain outside this case’s authority.

Fictional network · synthetic identities · no PHI · no production authority

RESEARCH / PUBLISHING

Righteous Recon

Gear should earn its place.

Gear research across six disciplines. Follow the sources, compare the tradeoffs, and see what still needs to be proven.

DEVELOPMENT EDITION Recorded September 24.

SOURCE RECORD 01 / 02 / RIGHTEOUS RECONGear should earn its place
Inspect this capture (opens the original file when inspection is unavailable)
RECORDED / 24 SEP 2026

Righteous Recon — The editorial direction

A recorded image. Zoom in and scroll to read closely; closing returns you to the page.

Righteous Recon development homepage with an editorial-preview banner and Gear should earn its place headline
Righteous Recon development homepage with an editorial-preview banner and Gear should earn its place headline
Full record24 SEP 2026
WHAT TO NOTICE

The development homepage pairs the research with its questions and sources. Its visible preview banner says publication approval is pending.

Recorded development edition · draft research · no approved recommendations
Source & recording details
Source page
Righteous Recon / development homepage
Displayed image
Full record · 24 SEP 2026
Date label source
Supplied metadata
Recorded edition
Historical development preview; exact render revision not recorded
06disciplines00approved product awards

This six-discipline direction is separate from the older 44-sector publication. The recorded preview contains no approved buying recommendations.

Open WESTFALL novel spread: a Brellford perimeter-route map beside the Part IV title page, ‘Brellford—Conscience costs everything.’
EXHIBIT 41-BBrellford perimeter route / Part IV
Open casefile

A research-grounded thriller
inside a fictional machine.

WESTFALL

Conscience Costs Everything.

TARGET RELEASE WINDOW

MO
--
Days
--
HRS
--
MIN
--
SEC
--
The story
A former ISA operator uncovers a private program inside Brellford National Group, a fictional Northern Virginia defense contractor.
The fracture
As the secret surfaces, the company turns on itself—forcing loyalty, betrayal, control, and free will into the same fight for survival.
The boundary
Real-world research grounds the machinery. Brellford, its people, and its hidden program remain fiction.

WRITING / CONTINUITY

JotterDown

The manuscript stays the authority.

A writing workspace that keeps track of your story as it grows. See which scenes, characters, and facts a change would affect before you make it.

SOURCE RECORD 01 / 03 / JOTTER DOWNThe page stays central
Inspect this capture (opens the original file when inspection is unavailable)
RECORDED / 20 OCT 2026

Jotter Down — A page at the center

A recorded image. Zoom in and scroll to read closely; closing returns you to the page.

JotterDown sample manuscript with character, place, object and source context
JotterDown sample manuscript with character, place, object and source context
Recorded frame20 OCT 2026
WHAT TO NOTICE

The sample keeps the manuscript in the center, with characters, places, and sources beside it. This is the frontdoor’s illustrative page, not a private manuscript.

Current frontdoor source · illustrative sample · no private manuscript
Source & recording details
Source page
JotterDown frontdoor source / sample panel
Displayed image
Recorded frame · 20 OCT 2026
Date label source
Supplied metadata
Recorded edition
Current GitHub frontdoor source rendered locally at 2× density; sample panel
Source revision
apps/web/src/pages/index.astro blob f2e25c79d2c810712c6616f231e155bbb5cfcc2d
01DRAFT02PREVIEW IMPACT03AUTHOR GATE

THE AUTHOR DECIDES The demo is read-only. Proposed changes need the author’s approval.

Writing tools and story continuity

JOTTER DOWN × CANONWEAVE / INTEGRATION STUDY

The page stays quiet.
The story stays connected.

A proposed home for timelines, character paths, and source trails beside the manuscript. Inspect a change, see what it touches, and keep the author in control.
SOURCE RECORD 01 / 01 / CANONWEAVEThe story stays inside
Inspect this capture (opens the original file when inspection is unavailable)
RECORDED / 22 SEP 2026

Canonweave — The story stays inside

A recorded image. Zoom in and scroll to read closely; closing returns you to the page.

Canonweave public access gate stating the private story room is author-only
Canonweave public access gate stating the private story room is author-only
Full record22 SEP 2026
WHAT TO NOTICE

The public response is an author-only access gate; no private workspace is pictured.

Protected author workspace · only its public access boundary is shown
Source & recording details
Source page
canonweave.zacgibson.work/
Displayed image
Full record · 22 SEP 2026
Date label source
Legacy filename
Generated integration concept: a quiet Jotter Down writing page beside a Canonweave dock with separate world and book order, character paths, source trail, and author review. All story content is synthetic.Loading image…
Proposed integration · generated design study · the products remain separateWriting page → source trail → author reviewInspect complete image (opens in a new tab)

Two orders, one story. World chronology stays distinct from the order a reader discovers it.

A source behind the connection. Character paths and continuity lead back to the material that supports them.

The author decides. Review creates an author-layer record; it does not silently rewrite a manuscript.

CRUX / PAPER RESEARCH

Private research.
Visible accountability.

A paper-research cockpit that turns an investment hypothesis into a record you can inspect over time. The public window exposes the aggregate mark, verification state, and timestamp. The research process stays inside the lab.

The public record
Mark. State. Time.Aggregate value · verification · timestamp
Execution boundary
Paper onlyNo broker connection. Nothing traded.

The pictured mark is a dated paper snapshot. Open the public window for its current reported value and verification state.

SOURCE RECORD 01 / 02 / CRUXThe paper record has a timestamp
Inspect this capture (opens the original file when inspection is unavailable)
RECORDED / 24 SEP 2026

CRUX — The dated paper mark

A recorded image. Zoom in and scroll to read closely; closing returns you to the page.

CRUX public paper portfolio showing its last complete September 23 valuation and recorded chart
CRUX public paper portfolio showing its last complete September 23 valuation and recorded chart
Full record24 SEP 2026
WHAT TO NOTICE

The public window records a September 23 close, viewed September 24. The source link is the place to check the next reported valuation.

Paper capital only · captured mark is historical, not a live quote
Source & recording details
Source page
crux.zacgibson.work/
Displayed image
Full record · 24 SEP 2026
Date label source
Supplied metadata

THE FULL COLLECTION

More to explore.

Browse the project index

Technology behind the work.

20 tool families

Tools and frameworks used across these projects, including AI-assisted implementations.

  • ChatGPT / Codex
  • Claude / Anthropic
  • Gemini / AI Studio
  • Python
  • TypeScript
  • React
  • Next.js
  • Astro
  • SwiftUI
  • Three.js / R3F
  • MCP
  • Tailwind CSS
  • shadcn/ui
  • Radix UI
  • Zod
  • Supabase
  • PostgreSQL
  • Cloudflare
  • GitHub
  • Suno

Let’s make something useful.

Tell me what you’re working on.

LET’STALKGet in touch