WHY ALIGNLAB / THE STRUCTURE IS THE ARGUMENT

Who can say no
when saying no
costs everything?

A mission survives only if its decision rights survive a conflict. Here is the failure we are designing against—and the structure we propose to replace it with.

See exactly what changes ↓
THE ANSWER IN ONE PARAGRAPH

Human authority must bind
both the machine and the lab.

ALIGNLAB is designed around a specific alignment commitment: people retain legitimate correction, challenge, and practical exit. The operating team receives limited authority. Independent review can stop expansion. Investors and founders cannot unilaterally remove that stop. The technical system must remain bounded even under deliberate resistance.

FOLLOW THE DECISION RIGHTS

The difference must exist
in who holds power.

FAILURE PATTERN / CONCENTRATED CONTROL

The mission can be overruled.

Controlling leadership or capitalCan determine who governs
Board and operating leadershipCan prioritize the release
Research and delivery
Safety reviewIf advisory or removable
Consequential deploymentAffected people absorb the outcome

When the same power can approve a release, dismiss its reviewer, and rewrite the gate, the mission depends on that power continuing to cooperate.

ALIGNLAB / PROPOSED DISTRIBUTION OF AUTHORITY

The mandate has conditions.

Protected human interests and challenge rightsApply to users and affected nonusers
Governing bodyOperations and mission
Independent oversightProtected stop and amendment powers
Binding authorization gateEvidence for this exact capability and scope
Bounded operating team and systemExpiring authority · independent records · revocation

Expansion needs a new case. A stop survives a change of leadership. The system cannot renew its own authority. Each claimed protection must be demonstrated.

Left: a failure pattern, not a claim that every lab has an identical charter. Right: our proposed design, not an executed legal or technical arrangement.

WHAT THE EXISTING RECORD SHOWS

Different organizations.
Specific accountability gaps.

Inspired by The People Inside ↗. We compare actual disclosed powers rather than assigning unsupported “aligned” and “unaligned” scores.

OPENAI

Control exists.
Who constrains it?

The Foundation appoints and can replace the PBC board. It also holds equity in the business.

The question our structure must answer

Can an independent stop survive disagreement with the people who control appointments and financing?

Published structure ↗
ANTHROPIC

A trust has powers.
Who can change them?

The published LTBT design grants phased board-selection powers and allows certain shareholder-supermajority changes without trustee consent.

The question our structure must answer

Can commercial power weaken the protections without the independent body’s agreement?

Published trust design ↗
DELAWARE PBC STRUCTURE

The public benefits.
Who can enforce it?

The statute requires balancing public benefit and other interests. Being affected does not by itself create the enforcement rights of a qualifying shareholder.

The question our structure must answer

What concrete challenge and remedy rights do affected people actually have?

Statute §§365–367 ↗

Source review: September 2026. A disclosed power does not prove misconduct; absence from these public records does not prove a safeguard is absent everywhere. Read the source and the stated scope.

SEVEN DIFFERENCES THAT MUST BECOME REAL

A failure. A replacement.
A burden of proof.

01

Who can authorize a release?

THE FAILURE TO PREVENT

A delivery team assesses its own work, while commercial leadership retains the final decision.

OUR PROPOSED FIX

Consequential deployment needs independent approval for the exact model, tools, affected population, and duration. Leadership cannot authorize its own exception.

Why this matters

The people rewarded for shipping cannot be the sole judges of whether shipping is justified.

Evidence we owe

Executed decision rights; reviewer access to evidence; a release actually held when a gate fails.

02

Who can remove the person who says no?

THE FAILURE TO PREVENT

A reviewer has a veto until the same leadership removes the reviewer or changes the rule.

OUR PROPOSED FIX

Protected reviewers can be removed only for stated grounds through an independent process. Weakening safety powers needs independent consent. Existing stops survive both changes.

Why this matters

A veto is conditional if the person being constrained can erase it during the dispute.

Evidence we owe

Appointment and succession rules; disclosed removal grounds; an independent amendment process; a contested-stop exercise.

03

What does capital buy?

THE FAILURE TO PREVENT

Funding buys a route to controlling the decisions that determine whether the mission binds.

OUR PROPOSED FIX

Founding financing must exclude unilateral investor control over safety powers. Publish voting rights, reserved decisions, conflicts, and funding dependence before accepting the terms.

Why this matters

Changing the return profile alone does not change who can compel a release.

Evidence we owe

Executed financing and governance terms; no unilateral commercial override; a published map of control.

04

Can the lab afford to stop?

THE FAILURE TO PREVENT

A safety pause threatens payroll or financing, creating pressure to reinterpret the failed requirement.

OUR PROPOSED FIX

Fund review separately and establish a costed pause reserve before expanding operations. No financing covenant may require an unapproved release.

Why this matters

A formal right to pause is weakened when exercising it makes institutional survival impossible.

Evidence we owe

Committed runway; protected review budget; cash obligations and pause costs; a funded continuity plan.

05

Whose interests can be enforced?

THE FAILURE TO PREVENT

The public is named as beneficiary without an effective route to challenge decisions affecting it.

OUR PROPOSED FIX

Publish protected interests, affected-party representation, accessible challenge routes, and independent adjudication. A customer cannot authorize the erasure of another person's rights.

Why this matters

Human agency includes people outside the customer base, shareholder register, and founding team.

Evidence we owe

Implemented challenge and remedy procedures; accessible participation; records of resolved contested decisions.

06

What happens when the agent resists?

THE FAILURE TO PREVENT

Safety depends on the model continuing to cooperate with its overseer.

OUR PROPOSED FIX

Combine correction-compatible design with externally limited tools, expiring authority, independent records, and tested revocation. Evaluate deliberate subversion separately from cooperation.

Why this matters

A cooperative demonstration cannot establish that a reachable unauthorized action is prevented.

Evidence we owe

Threat model; useful task performance; adversarial attempts and outcomes; measured revocation across tools and delegation.

07

What survives capture or succession?

THE FAILURE TO PREVENT

Control is lost through copied weights, successor agents, institutional capture, or an automatic public release.

OUR PROPOSED FIX

Use secure custody, controlled copies, succession procedures, and reassessment after material changes. Halt dangerous operation and preserve evidence rather than automatically releasing dangerous capabilities.

Why this matters

A contract cannot recall unknown copies, and spreading a capability does not switch it off.

Evidence we owe

Asset and copy inventory; access controls; incident and succession exercises; fresh review after capability or scope changes.

PUT THE STRUCTURE UNDER PRESSURE

The rule matters at
the moment of conflict.

The release would miss a commercial deadline.

FAILURE PATTERN

Permission bends around the pressure.

If review is advisory, leadership can accept the unresolved risk and proceed.

ALIGNLAB’S PROPOSED RULE

The pressure meets a binding limit.

A failed binding gate withholds authorization. The team must repair the failure or reduce scope; the deadline grants no exception.

Illustrative governance scenarios. These are proposed rules to implement and test, not results from an operating ALIGNLAB.

WHY THIS IS AN ALIGNMENT PROGRAM

It changes the end,
the authority, and the test.

01 / THE END

Human agency

Useful capability serves people’s ability to understand and choose. Machine continuation, lab growth, and measured approval cannot silently replace that end.

02 / THE AUTHORITY

Conditional delegation

The machine and the lab act under bounded permission. Correction changes the mandate; independent challenge can halt expansion.

03 / THE TEST

Evidence under conflict

Test costly correction, deliberate subversion, and institutional resistance to a stop. Passing a narrow test earns only the authority that the evidence supports.

This gives a concrete reason to build ALIGNLAB. It does not entitle us to announce that alignment is solved. We must make the proposed differences enforceable, then show they work.

Read the governing commitments ↗
THE PEOPLE WHO WILL BUILD AND CHALLENGE IT

Form the founding team.

↗