IT SYSTEMS / DOCS
Documentation
Architecture, rules and programmes explained clearly. Each page separates the concept, its governing authority and its current integration state.
LOGOS-1: architecture and human control
LOGOS-1 is a research and architecture programme for governable AI over time. The Company Brain is an integration goal for enterprise knowledge and tools, not a blanket claim of a finished product.
Continue reading →Γ: the boundary between proposal and effect
Γ is a non-learning assurance boundary for proposed effects. It holds no goals of its own and creates no authority.
Continue reading →BIO Code: biology as a testable design source
BIO Code studies mechanisms from living systems as engineering candidates. Proteins and their interactions offer analogies, not directly transferred software or permission.
Continue reading →Atomic Rules: small rules that survive architecture changes
Atomic Rules preserve basic distinctions so higher system layers cannot quietly redefine safety boundaries.
Continue reading →AKAC: check access before search and release
AKAC is a separate access layer for sources, tools and derived content. A search result is not a read permission.
Continue reading →Decision model: review proposals without inventing rights
The decision model classifies signals and risks. It may tighten a review but cannot loosen an existing rule or human approval.
Continue reading →Referral programme: one project
Project referrers may introduce a specific contact with their consent. Partner membership is not required.
Continue reading →Partner programme: membership
Membership is for companies that regularly introduce projects and want a separate partner agreement.
Continue reading →