ACE-LAB-GATEWAY

Status

ACTIVE_LAB_UNDER_CADRED.

This repository is a public lab surface for ACE-adjacent experiments, currently including generated 3D / Blender / gallery artifacts and gateway scripts.

It is not the ACE cockpit, not AV0, not the trading bridge, not a provider surface, not a wallet surface, not a deployment surface, and not a permission-to-act mechanism.

Role

ACE-LAB-GATEWAY is a lab repository.

It may contain experiments, generated artifacts, prototypes, visual outputs, gateway scripts, and exploratory material that could later be reviewed from the ACE cockpit.

Its current role is:

LAB_EXPLORATION_SURFACE
NOT_GOVERNED_RUNTIME
NOT_ACE_AUTHORITY

LivingBureau extraction

The local V3-LivingBureau prototype is treated as source material, not as a direct merge artifact.

The safe integration path is:

prototype capture
-> status contract
-> atomic JSON writer
-> Board Control read-only observation adapter

Current reviewable extraction files:

• docs/LIVINGBUREAU_PROTOTYPE_CAPTURE_V0.md
• docs/LAB_GATEWAY_TO_BOARD_CONTROL_CONTRACT_V0.md
• schemas/lab_gateway_status.schema.json
• examples/lab_gateway_status.example.json
• System/runtime_paths.example.json
• System/lab_gateway_writer.py

These files do not open runtime, call providers, call Gemini, connect wallets, write secrets, deploy services, or grant permission-to-act.

Relation to other repositories

Repository	Relationship
monkidy/asso-execution-bridge	Primary ACE / Asso cockpit and source of current operational truth. Any governed integration or status change for this lab must be recorded there first.
monkidy/ace-av0	Zone C / AV0 satellite. This lab is not AV0 and must not imply avatar continuity, presence, sovereignty, or memory authority.
monkidy/ai-ops-sop-pack	Public SOP documentation pack. This lab is not a SOP publication or commercial artifact.
monkidy/ACE	Empty placeholder repo, not active.

Current boundaries

This repository does not authorize:

• ACE doctrine changes;
• AV0 identity or avatar-presence claims;
• live trading;
• provider access;
• wallet access;
• secrets;
• .env writes;
• deployment;
• runtime monitoring;
• background daemons;
• cross-repo automation;
• permission-to-act.

Lab discipline

Until a proper gate is created, all work here should be treated as lab material.

Allowed by default:

• static files;
• visual / 3D / generated artifacts;
• documentation;
• prototype scripts treated as untrusted until reviewed;
• manual inspection.

Not allowed by default:

• execution claims;
• production claims;
• wallet/provider integration;
• secret handling;
• automatic sync into ACE or AV0;
• treating generated artifacts as proof of authority;
• treating scripts as safe without static review.

Required before governed integration

Before this repo is treated as a governed ACE satellite, file or link:

LAB_GATEWAY_SCOPE_V0
LAB_GATEWAY_SCRIPT_SAFETY_CLASSIFICATION_V0
LAB_GATEWAY_ARTIFACT_PROVENANCE_V0
LAB_GATEWAY_RELATION_TO_ASSO_AND_AV0_V0
LAB_GATEWAY_CLOSEOUT_PROTOCOL_V0

The first authoritative cross-repo mapping is recorded in:

monkidy/asso-execution-bridge:
docs/ace_canon/repo_topology/ACE_REPO_TOPOLOGY_REGISTRY_V0.md

Next gate

Recommended next gate:

LAB_GATEWAY_SCOPE_AND_ARTIFACT_MAP_V0

Purpose:

• map existing generated artifacts;
• identify scripts and side effects;
• classify what is static, generated, executable, or unknown;
• decide what, if anything, should later connect to ACE or AV0.

Current decision

LAB_ONLY
NO_GOVERNED_INTEGRATION_YET
NO_RUNTIME_AUTHORITY
NO_PERMISSION_TO_ACT