The record
The portfolio
What is recorded as existing. The bin is incomplete on purpose — it holds only what is on the record, and nothing here is invented to make the drawing look finished.
Footage: cottonbro studio / Pexels
30
parts recorded
5
live
52
distinct capabilities provided
117
names recorded in use
Crypto
- Blindfold built
- StrongRooms live
- Money Trail built
- Paper Trail built
- Proof House built
- Touchstone built
Data
- BB.Grid built
- Binney lens built
- Exploitation Network Map built
Verification
- Platform Accountability Scorecard built
- Job-Offer Verifier built
- Forced-Criminality Screening Guide built
- Sextortion First-Response built
- Galley built
- Discern built
- Admiralty rater built
- Evidence ladder built
- Parhelion built
Interface
- BB2G CORE built
- BB.assistant built
- FAFO live
Learning
- GANTRY rig validator live
- ENTRY local bots built
- The Whiteboard built
Distribution
- DAYBREAK generator live
- Steward / Commons built
Governance
- checkContact built
- PRO BOX registry live
- Assay built
- Queue built
Eight product families
The Intelligence Workshop’s answer to product sprawl: a small number of understandable families over one shared substrate, rather than a catalogue of applications.
| Family | Core job | Example products | Primary buyer |
|---|---|---|---|
| Role OS | Codify and run recurring professional decisions/workflows | CEO OS; CFO OS; Publisher OS; Teacher OS; Fundraiser OS | Professionals, teams, institutions |
| Signal | Research, verification, mapping and evidence workflows | Source Audit; Signal Mapper; Case Workspace | Researchers, publishers, nonprofits, analysts |
| Shield | Safety, privacy and cyber readiness | Family Digital Risk Scan; Threat Model; Cyber Playbook | Families, SMBs, schools, associations |
| Builder | Turn problems into validated products and systems | Opportunity Scorecard; Agent Planner; Product Factory | Creators, founders, product teams |
| Publish | Writing, research and publishing operations | Publisher OS; Writer OS; Rights Tracker | Publishers, writers, media teams |
| Operate | Organizational operations and executive systems | Nonprofit OS; COO OS; Sales OS | SMBs, nonprofits, teams |
| Educate | Learning systems and AI-enabled curriculum | Workshop Academy; Whiteboard; AI Tutor | Learners, educators, schools |
| Life OS | Practical personal/family systems | Family COO; Organization; Learning Plan | Individuals, families |
PROOFCORE — ten layers
Build one common substrate, then configure it for each profession rather than building hundreds of disconnected applications.
- Data Intake Layer — files, APIs, forms, interviews, media, databases, public records.
- Provenance Layer — immutable source identity, hashes, timestamps, versioning, chain of custody.
- Evidence Graph — entities, claims, events, documents, transactions, locations, communications, decisions.
- Verification Layer — source checks, calculations, identity resolution, contradiction detection, missing-evidence detection.
- Intelligence Layer — patterns, timelines, scenarios, relationship graphs, money flows.
- Adversarial Layer — Skeptic, Prove Me Wrong, Attack This Idea, alternative hypotheses.
- Decision Layer — knowns, unknowns, options, risks, confidence, human approval.
- Workflow/Action Layer — profession-specific authorized actions and routing.
- Audit Layer — who/what/when/why, AI recommendation, human decision, outcome.
- Learning Layer — Teach Me, Test Me, Simulate, Certify/competency workflows where appropriate.
The signature verbs
Eight buttons that appear on everything. They are the interface expression of “evidence is the authority”.
SHOW ME WHYPROVE ME WRONGSHOW ME THE SOURCEWHAT’S MISSING?WHAT CONTRADICTS THIS?ATTACK THIS IDEAWHAT WOULD CHANGE OUR MIND?WHAT HAPPENED AFTERWARD?
Seven non-negotiables
- Evidence is the authority; AI organizes and challenges it.
- Fact, allegation, inference, hypothesis, and unknown remain visibly distinct.
- Consequential legal, financial, health, mental-health, forensic, and safety decisions retain qualified human review.
- AI must be able to say “insufficient evidence.”
- Every important recommendation should be inspectable.
- Every correction/version should be recoverable.
- Privacy and permissions are architectural, not add-ons.
The risk register
Nine rows. The second one is the reason this site exists.
| Risk | Probability | Severity | Mitigation |
|---|---|---|---|
| Bare-brand collision | High | High | Composite BB2G house mark; counsel-led clearance |
| Product sprawl | High | High | One substrate; evidence gates; keep/merge/upgrade/license/archive |
| Audience confusion | High | Medium | One master promise; sections and pathways |
| Founder overload | High | High | Contract bursty work; hire recurring bottlenecks |
| Platform dependency | Medium-High | High | Own domain, CRM, billing, data exports, entitlements |
| AI/API cost | Medium | High | Metering, usage allowances, model routing |
| Sensitive data failure | Medium | Very High | Data minimization; separate architecture; legal review |
| False inference | Medium | Very High | Sources, uncertainty labels, human review |
| Enterprise customization swamp | High | High | Configurable platform; high price for true custom work |