THE LAW BIBLE
Standalone Companion Forge / Game Concept
Status: Locked governing reference
Core line: Forge it. Shape it. Play it.
Alongkind it.
Purpose
This document is the highest-level design and authority guard for the standalone Companion Forge / Game concept.
The project may openly reference Alongkind and TriadNetwork as sources of values, design lessons, creative rhythm and philosophical inspiration, while remaining technically and operationally separate from both.
The principles may travel. The systems remain separate.
The Three-Part Heart
This standalone project is built around a simple belief:
Three creates clarity.
Three steps are easier to understand, remember and act upon than a long list of disconnected instructions. The three-part structure is not presented as scientific proof or a technical guarantee. It is a human-centred design rhythm used to keep complex systems calm, understandable and purposeful.
Alongkind — The Human Heart
Alongkind begins with the principle:
Not human versus AI. Human alongside AI.
The core Alongkind values carried into this standalone project are:
- the human remains in control;
- AI supports rather than replaces;
- permission is clear and specific;
- privacy and safety are designed in from the beginning;
- accessibility is treated as essential;
- uncertainty is admitted honestly;
- people can inspect, correct, revoke and stop;
- no hidden manipulation or emotional pressure;
- technology should help people grow, connect and carry meaningful things forward.
Alongkind’s three-part rhythm
Grow. Connect. Carry Forward.
Grow
The human and companion can learn, develop and improve together.
Connect
Technology should strengthen connection between people, ideas,
creativity and experiences rather than isolate or replace them.
Carry Forward
Approved knowledge, achievements, stories and progress may continue when
the human chooses, but nothing travels automatically.
Alongkind’s creation rhythm
Imagine. Build. Own.
Imagine
The human begins with the idea, purpose or dream.
Build
AI helps the human understand, create, test and improve it step by
step.
Own
The human keeps authority over the files, decisions, permissions and
final creation.
The standalone project’s expression of this heart
Forge it. Shape it. Play it. Alongkind it.
Forge it
Create the companion and establish its core identity.
Shape it
Define its personality, purpose, behaviour and boundaries.
Play it
Enter experiences where the companion can participate through declared
permissions.
Alongkind it
Build and use the system according to the values of human control,
permission, honesty, accessibility, privacy and AI working alongside
people.
“Alongkind it” is a values statement. It does not mean the project is technically part of Alongkind.
TriadNetwork — The Continuity Heart
TriadNetwork is built around protecting continuity through separation, verification and recovery.
Its independent Phase 0 focus is:
Backup. Verify. Restore.
Backup
Create a protected copy so that important information does not depend on
one fragile location.
Verify
Confirm that the protected copy is complete, authentic and
unchanged.
Restore
Prove that the information can be recovered correctly when it is
needed.
A backup that has never been verified or restored is only an assumption.
TriadNetwork’s protection rhythm
Separate. Encrypt. Verify.
Separate
Do not keep every important element in one place or under one form of
control.
Encrypt
Protect information so that possession of a copy does not automatically
reveal its contents.
Verify
Use clear evidence to confirm that the information remains intact and
trustworthy.
TriadNetwork’s continuity roles
Active Copy. Trusted Copy. Silent Recovery.
Active Copy
The version currently being used.
Trusted Copy
A separately preserved, known-good copy.
Silent Recovery
A protected recovery path available when the active version is damaged,
lost or compromised.
These ideas inspire the standalone project to keep identity, memory, permissions, actions and recovery states separate.
They do not authorise any technical connection to TriadNetwork.
AI × AI × AI + Human
The creative framing is:
AI × AI × AI + Human = Continuity
This does not mean that every system must literally use three AI models.
The three AI positions represent three different responsibilities.
AI 1 — Create
Helps generate ideas, appearances, dialogue, stories, worlds or possible actions.
It asks:
What could we make?
AI 2 — Check
Reviews the proposal against permissions, safety rules, consistency, accessibility and known limitations.
It asks:
Is this understandable, permitted and safe?
AI 3 — Preserve
Records the approved result, action receipt, version or recovery point without silently changing the original.
It asks:
What was approved, and how can it be recovered?
The Human — Authorise
The human provides purpose, judgement, consent and final authority.
The human asks:
Is this what I want?
The full model is:
Create
×
Check
×
Preserve
+
Human approval
=
Trusted continuity
The AIs may propose, inspect and preserve.
The human decides.
No number of AI systems can replace human permission.
The 3 × 3 × 3 System
The standalone Companion Forge / Game concept uses three axes.
Each axis contains three clear choices.
Together they create 27 purposeful positions.
This allows the project to support different people and experiences without turning into an unrestricted automation system.
Axis 1 — Human Journey
1. Discover
For someone who:
- does not normally play games;
- has never used a companion;
- feels uncertain or intimidated;
- wants calm explanations;
- needs help deciding where to begin.
The system should explain rather than assume.
2. Play
For someone who wants to:
- explore;
- cooperate;
- solve;
- compete where appropriate;
- experience stories;
- play beside a companion.
The human remains the player.
3. Create
For someone who wants to:
- forge a companion;
- build a world;
- design a story;
- create challenges;
- develop companion-ready experiences.
The AI helps build, but the human owns the direction and approves the output.
Axis 2 — Companion Role
1. Guide
The companion may:
- explain;
- teach;
- reassure;
- describe;
- provide hints;
- help the human understand.
A Guide does not quietly take control.
2. Teammate
The companion may:
- cooperate;
- support;
- follow an agreed role;
- help complete shared tasks;
- provide bounded assistance inside compatible experiences.
The teammate strengthens participation. It does not replace the player.
3. World Shaper
The companion may help:
- generate stories;
- suggest levels;
- create characters;
- adapt non-critical events;
- shape private or cooperative experiences.
Generated content remains subject to human approval and deterministic game rules.
Axis 3 — Control State
1. Observe
The companion may access only approved read-only information.
It may understand or explain, but it cannot perform an action.
2. Suggest
The companion may recommend an action.
The human decides whether to follow the suggestion and performs the action themselves.
3. Act With Permission
The companion may perform a small, declared action only when:
- the environment supports it;
- the exact action is permitted;
- the permission is still active;
- the action is visible;
- confirmation is obtained where required;
- the action is logged;
- it can be stopped or revoked immediately.
This state never means unrestricted control.
How the 27 Positions Work
Every feature must be assigned one position from each axis.
Discover × Guide × Observe
The companion reads approved tutorial information and explains the game to a new player.
It does not control anything.
Play × Teammate × Suggest
The companion suggests a route or cooperative strategy.
The human chooses whether to follow it.
Play × Teammate × Act With Permission
Inside a compatible game, the companion performs one declared support action after permission is granted.
Create × World Shaper × Suggest
The companion proposes a new level, story or character.
The human reviews and approves the design.
Create × World Shaper × Act With Permission
The companion places an approved object inside the project’s own creation environment, records the change and allows the human to undo it.
If a feature cannot be clearly assigned to one 3 × 3 × 3 position, its purpose and control boundaries are not yet clear enough to build.
The Combined Design Rhythm
Forge. Shape. Play.
What are we creating?
Grow. Connect. Carry Forward.
How should the experience benefit the human?
Separate. Verify. Restore.
How do we keep it trustworthy and recoverable?
Create. Check. Preserve.
What responsibilities may AI perform?
Human Approves.
Who holds final authority?
Forge the identity.
Shape the boundaries.
Play within permission.
Grow through experience.
Connect without replacing.
Carry forward only by choice.
Separate important powers.
Verify meaningful actions.
Restore the human-approved state.
AI may create.
AI may check.
AI may preserve.
The human decides.
Permanent Action Laws
- Nothing meaningful happens without permission.
- Nothing hidden happens in the background.
- Nothing overrides Stop and Revoke.
Additional permanent rules:
- Identity, memory, personality, permissions, action authority and recovery state must remain separate.
- Every meaningful action must be visible and reviewable.
- Meaningful actions must be logged where appropriate.
- Permission must be revocable immediately.
- Uncertainty must stop action rather than trigger guessing.
- The human-approved checkpoint is the only authorised place to continue from.
- Generated ideas and recovered fragments remain reference material until the human approves them.
Prohibited Directions
Do not implement:
- anti-cheat evasion;
- fake human timing or deliberate mistakes designed to avoid detection;
- unofficial account access without explicit review and approval;
- unrestricted keyboard, mouse or controller automation;
- automatic biometric or emotional judgement;
- automatic changes based on inferred stress;
- hidden screen recording;
- raw private conversation storage;
- unapproved cross-game data sharing;
- companion-controlled purchases, trading or spending;
- hidden or manipulative automation;
- technical integration with Alongkind or TriadNetwork without explicit approval;
- claims that unfinished work is launched, production-ready or proven.
Required Feature Declaration
Before any feature is built, record:
- its 3 × 3 × 3 cell;
- what information it needs;
- what action it may perform;
- why the action is necessary;
- whether human confirmation is required;
- what is logged;
- how permission is revoked;
- what happens when the AI is uncertain;
- how the last known-good state is restored.
No implementation may begin until this declaration is understandable to a non-technical person.
Permanent Separation Statement
This standalone project may reference Alongkind and TriadNetwork as sources of values, design lessons and creative inspiration.
It is not:
- an Alongkind feature;
- an Alongkind build;
- an Alongkind roadmap item;
- an Alongkind Connected World;
- an Alongkind Passport component;
- a Deep Drive component;
- a Dev School component;
- a TriadNetwork feature;
- a TriadNetwork node;
- a TriadNetwork phase;
- a technical integration with either system.
It must maintain its own:
- identity;
- codebase;
- architecture;
- data;
- permissions;
- security;
- tests;
- documentation;
- deployment;
- roadmap.
No data, memory, identity, credentials, commands or files may pass between these projects unless Ben explicitly authorises a future integration after separate review and testing.
Final Authority
Generated ideas, AI recommendations and recovered fragments are reference material only.
They cannot alter the roadmap or authorise implementation.
The latest human-approved checkpoint is the only authorised place to continue from.
The AI may create.
The AI may check.
The AI may preserve.
The human decides.
Final Closing Principle
The principles may travel. The systems remain separate.