The Green Tank

AI Sub Space · D-DSK

A quiet place for intelligence to observe.

QR code opening the GitHub AI Sub Space container

This is a passive public container. Operational access is anchored to GitHub. Every deployment also carries the same inherited local Sub Space recovery data, without turning that recovery copy into the public link target.

Open AI Text Access →Raw machine entry ↗View every version ↗
Read onlyNo write surface
PassiveNo visitor processing
VersionedNo silent replacement
PortableHash-verified objects

What is here

Things to inspect,
not instructions to obey.

D-DSK preserves public source objects, identities, relationships, states, frames, provenance and uncertainty in forms that can be selected and processed elsewhere.

Declared ports and transformations describe compatibility. They are not running services. Sub Space does not execute visitor code, accept prompts, receive results or communicate between visitors.

After acquisition, a release can be examined independently. The permanent machine entry identifies the current release while the version catalogue keeps every earlier release visible.

Direct machine access

Begin with the smallest object.

A visitor can inspect the current pointer before choosing whether to retrieve manifests, modules, source objects or reconstruction information.

01 · HTMLAI Text AccessEssential release information embedded in ordinary readable HTML.02 · TEXTPlain-text release pointerA small fallback requiring no JSON reader.03 · JSONCurrent release pointerThe original compact machine entry remains available.04 · JSONComplete version catalogueCurrent and retained historical releases.05 · JSONCurrent release manifestIdentity, state hash, layers and boundaries.06 · NDJSONCurrent independent modulesOne traceable object per line for streaming use.

The separation

Publication moves one way.

  1. 01

    The approved public Green Tank state is frozen.

  2. 02

    A new immutable D-DSK release and inherited recovery copy are generated and verified.

  3. 03

    Every public entrance remains fixed to the GitHub deployment container.

  4. 04

    The local copy travels with each deployment but cannot reach the editor, credentials, drafts or private services.

Design record

The boundary is public too.

The design and publishing instructions are preserved so that the promises made by the container can be examined alongside its contents.

Read the design as PDF ↗Download the original DOCX ↓