Boundaries to clarify before real-world use

Why this mechanism is needed, and how far it may go

When AI or AGI enters different real-world tasks, crisis response, cognitive safety, permissions and long-term coordination are not the same problem. A single “latest version” cannot therefore cover every task.

Who has authority to decide

Permissions derive from the real task, authorization, phase and applicable jurisdiction. Combining tracks must not automatically accumulate permissions. Machine-side safety cannot replace human responsibility.

What it can do

Select applicable tracks according to the real problem, limit permissions, and establish auditing, stopping, human takeover and phase boundaries.

What it cannot do

No version automatically acquires real-world sovereignty or may expand its powers without limit in the name of safety. The controlled version family must not be described as a linear upgrade culminating in one supreme version.

How to test whether it actually works

Validate through sandboxes, controlled tests, independent audits, stopping drills, permission tests and real-world chains of responsibility.

When to stop, exit or roll back

If operation cannot be stopped, permissions exceed their boundaries, auditing fails, a track is applied in the wrong phase, or human and machine responsibilities become confused, stop, roll back or switch to a track with fewer permissions.

How real-world results revise upstream design

Use test results to revise track applicability, permission boundaries and the interfaces with Human-COS and Nebula.

AGI-COS has no single “latest version.” This is a controlled navigation entry: choose a track by the actual problem, stage or phase, task and permissions, then enter the corresponding professional source text.

The problem this work addresses

AGI-COS has no single “latest version” that covers every work. First choose a version track by the actual problem, stage, environmental phase, task process state, responsibility and authorization. Tracks may be combined; permissions may not be stacked.

Place in the framework

This work belongs to the AGI-COS family in the AGI governance and civilizational safety field. Its current role is a one-page guide to the controlled version family.

Who should read it

General readers, decision-makers, engineers and researchers

Reading guidance

If you are unsure which AGI-COS version to open, begin here; then consult the G-03 controlled version map and the relevant professional source text.

Version and publication status

Current version
V1.0
Publication status
Current controlled navigation
Role of this work
One-page controlled version-family entry
Stable English page
https://www.civitas.top/en/documents/p05-agicos-011/

Continue reading

Publication boundaries

This page describes the current controlled public version only. Audience-specific editions, research tracks, historical versions and engineering details retain their respective authority. Public explanation does not create new theory, permissions or authority to deploy.

Translation scope

This page translates the public web description. The reviewed English manuscript is available in the English PDF section below; its source edition is identified there.

Cite this English description page

AGI-COS Controlled Version Family: A One-Page Guide by Stage. V1.0. English description page. https://www.civitas.top/en/documents/p05-agicos-011/

This citation identifies the English description page, not a claim that the complete manuscript or every attachment is available.

English PDF

Download the English PDF · V1.0