Nicholas Dunzelman

Scale engine · generated 2026-05-19T14:58:23Z

Autonomous growth is a flywheel stack, not a promise of guaranteed size.

Build the company toward frontier-lab category completeness: product proof, developer trust, safety/governance, distribution, hiring/collaboration leverage, and public evidence. This is an operating target, not a claim that CIW has matched OpenAI, Anthropic, DeepMind, or any other frontier institution.

This engine is not guarantee language. It creates compounding work loops while preserving no legal formation claim, no payment or checkout activation, no hiring or compensation promise, no fundraising claim, no customer or revenue claim, and no affiliation or endorsement claim.

Autonomy may select, build, test, render, scan, publish, and ledger public-safe proof work. Autonomy may not cross no outbound, no legal, no payment, no hiring, no fundraising, no contract, no customer, no revenue, no affiliation, no trademark, or no private-data gates without a separate current authorization and the required external review.

openai-careers

OpenAI Careers

Career credibility is treated as a visible institution surface: mission, teams, programs, roles, and current openings are public paths.

source

openai-interview-guide

OpenAI Interview Guide

The role route should show fast learning, collaboration, feedback openness, and concrete evidence instead of generic credential signaling.

source

openai-developers

OpenAI Developers

A serious AI company needs developer-facing docs, examples, community routes, status visibility, and reusable build patterns.

source

openai-startups

OpenAI for Startups

Builder programs make growth legible through resources, events, office-hours style support, and founder-focused education.

source

openai-brand

OpenAI Brand Guidelines

Brand safety is a growth requirement: do not imply relationship, sponsorship, endorsement, or confusing official status.

source

openai-policies

OpenAI Policies

Durable scale needs policy awareness, not only product speed: terms, usage boundaries, and safety expectations shape what can be built.

source

anthropic-company

Anthropic Company

Anthropic frames itself around safety and research; the reusable pattern is making governance and technical direction first-class public evidence.

source

proof-compounding · live

Proof Compounding

Every meaningful work unit becomes a validator, receipt, public page, graph node, and source-backed reviewer surface.

Autonomous action
Select one non-redundant verifier-backed proof gap, build it, run tests, export public-safe data, and ledger the receipt.
Proof metric
Verifier passes plus public graph/ledger counts move after each shipped artifact.
Scale failure
A strategy memo with no command, fixture, source, public page, or hash-chain receipt.

developer-distribution · candidate

Developer Distribution

Turn each internal proof behavior into docs, examples, recipes, route indexes, and inspectable demos that a builder can traverse without private context.

Autonomous action
Promote runnable proof into a public-safe page only after privacy, banned-claim, link, and source checks pass.
Proof metric
Public URL markers pass and verifier-backed examples exist for each promoted behavior.
Scale failure
A broad marketing page that explains the company without giving a developer anything executable or inspectable.

safety-governance · live

Safety Governance

Every launch or leverage claim is downgraded unless the claim boundary, privacy scan, and readiness ratchet can defend it.

Autonomous action
Refuse unsafe claims, rerender boundary docs, and keep legal/commercial stages blocked until explicit qualified review exists.
Proof metric
Public banned-claim scans and verifier commands pass before publishing or route use.
Scale failure
Borrowing frontier-lab language so closely that a reader could infer affiliation, endorsement, customers, funding, or official status.

agent-labor · watch

Agent Labor

Specialized agents research, build, verify, review, publish, and update the map while deterministic scripts keep them inside gates.

Autonomous action
Use subagents for independent research or file-scope work, then merge only source-backed and validator-backed outputs into CIW artifacts.
Proof metric
Autonomy heartbeat, tests, rendered pages, and public-safe scans pass after agent-produced changes.
Scale failure
Parallel work that creates unverified notes, duplicate artifacts, stale pages, or unsupported company claims.

market-learning · date_gated

Market Learning

Public proof and benchmark research become hypotheses, then verified replies, user inspection, or post-gate outreach convert them into actual market evidence.

Autonomous action
Before the gate, only build benchmark scans, refusal rules, and no-send packets; after the gate, refresh evidence before any message.
Proof metric
Public-safe outcome watch and signal router classify real evidence before any leverage branch can move.
Scale failure
Treating page views, application receipts, or benchmark similarity as customer traction.

capital-readiness · blocked

Capital Readiness

Company formation, finance, paid pilots, hiring, fundraising, and contracts become eligible only after separate legal/admin/payment review.

Autonomous action
Maintain the blocked backlog and convert gaps into questions for qualified review; do not activate money movement or commercial claims.
Proof metric
Public readiness pages continue to state the legal/commercial company is blocked until verified external review changes it.
Scale failure
Pretending the proof lab has customers, employees, revenue, investment, incorporation, or authority it does not have.
Strategy Selector Heartbeat finds no required failure and the growth plan exposes a non-redundant safe branch. Growth plan JSON, graph node, and passing verifier. No outbound and no legal/commercial move; repair failed gates before strategy.
Builder Lane Selected branch needs code, page, fixture, or data-model work. Unit tests, render command, and diff-limited file list. No outbound and no legal/commercial move; stop on unowned destructive edits.
Verifier Lane Any artifact is promoted from note to proof. Failing fixture for unsafe cases and passing fixture for valid cases. No outbound and no legal/commercial move; refuse proof without a runnable check.
Source Lane Benchmark, role, policy, platform, or competitor facts influence public strategy. Source-backed memo with date, URL, and claim boundary. No outbound and no legal/commercial move; do not use stale or unsourced claims.
Public Surface Lane Graph, ledger, route index, digest, or page content changes. QA pass plus public marker pass or exact deploy blocker. No outbound and no legal/commercial move; do not publish private paths or confusing marks.
Safety Lane A copied pattern, benchmark claim, growth claim, or protected mark appears. Banned-claim scan, privacy scan, and claim-boundary note. No outbound and no legal/commercial move; do not let ambition override source truth.

live

Proof Lab

Local verifier-backed artifacts exist and CIW has its own name, charter, proof ledger, and graph.

Stale graph, broken verifier, private leakage, or generic proof.

live

Public Trust

Pages route, reviewer digest, ledger inspector, system map, and autonomy status are public and scanned.

Missing source basis, confusing claims, stale public URLs, or unreadable route structure.

date_gated

Collaboration Leverage

Verified human-owned or target-company-owned signal appears, or the post-2026-05-26 outcome refresh opens a safe route.

Application receipt only, no-outbound gate, ambiguous signal, or unsupported claim.

blocked

Legal Company

Explicit current user instruction plus qualified legal/admin/tax/trademark review.

No legal review, no entity, no trademark clearance, no tax setup, and no contract authority.

blocked

Commercial Scale

Legal company stage clears and payment, support, customer, security, and contract systems are authorized.

No payment authorization, no customers, no revenue, no contracts, no support system, and no verified commercial deployment.