black O2, inc.
ACTIVE
    FOR-001 / ConceptsCON-010

    Walled garden

    Active concept

    title
    Walled garden
    Type
    concept
    Identifier
    CON-010
    Status
    Active
    Tags
    • architecture
    • policy
    • boundary
    Aliases
    • closed deployment
    • operator enclave
    connections
    • [[CON-008]]
    • [[CON-009]]
    • [[QST-004]]
    source path
    sources/shackled-ai-themes-in-sci-fi.md

    Walled garden

    A deployment in which the system's knowledge, tools, and record of interaction are confined to the operator's boundary — reachable by the operator, unreachable by the developer, the platform, or third parties.

    Why The Term Is Precise Here

    A walled garden is usually a euphemism for lock-in: the vendor walls the customer in. Here the wall runs the other way. The garden is walled against the developer, and the operator is inside it. That inversion is the whole point of the Citadel proposal, and it is why the legal instrument (CON-008) and the architectural one (CON-009) have to arrive together.

    What The Wall Must Withstand

    • Developer-side telemetry — the ordinary product path by which a deployment reports home.
    • Compelled disclosure — a warrant served on the party that can read the data.
    • Model-level extraction — an agent persuaded or induced to disclose its own context.

    The third is why the wall cannot be built only in policy or only in the model. It has to be built where the agent's action space ends.

    Connections

    • MAP-003 — the stack that builds the wall.
    • CON-002 — the principle the wall instantiates.

    Back to Shackled AIForests