Atlas — On-Chain Package Registry

Each OS maintains an Atlas — a TSP-2 Card collection for packages. Packages are Cards. Publishing is minting. Updating is metadata update. The registry reuses the same PLUMB framework that powers all tokens.

See Atlas: Why On-Chain Package Management for design rationale.

1. Registry Model

Each OS has its own Atlas collection with independent mint authority.

2. Package Card Format

Card Leaf (TSP-2) — 10 field elements

leaf = hash(asset_id, owner_id, nonce, auth_hash, lock_until,
            collection_id, metadata_hash, royalty_bps, creator_id, flags)

Package Metadata — 10 field elements

metadata = hash(name_hash, version_hash, source_hash, program_digest, dependencies_hash,
                verification_cert, tags_hash, compiler_version, 0, 0)

3. Operations

Publish (Mint — Op 3)

1. Mint authority required (per-OS governance)
2. asset_id = hash(package_name) — must not exist (non-membership proof)
3. metadata_hash = content_hash(artifact + metadata)
4. creator_id = publisher_id (immutable forever)
5. flags = TRANSFERABLE | UPDATABLE | BURNABLE (standard package)
6. nonce = 0, lock_until = 0
7. New leaf inserted into Atlas Merkle tree
8. asset_count incremented

Update (Op 2)

1. Owner auth required, flags & UPDATABLE checked
2. Only metadata_hash changes (new version artifact)
3. Old version content remains accessible by its content hash
4. nonce += 1 — provides version ordering

Transfer Ownership (Pay — Op 0)

1. Standard TSP-2 Pay constraints, flags & TRANSFERABLE checked
2. owner_id and auth_hash change
3. creator_id, collection_id, metadata_hash, flags unchanged

Deprecate (Burn — Op 4)

1. Owner auth required, flags & BURNABLE checked
2. Leaf removed from Atlas Merkle tree, asset_count decremented
3. Name freed for re-registration (asset_id slot available)
4. Existing content hashes remain valid (content-addressed storage)

Search / Resolve

4. Three-Tier Resolution

use my_package.module

1. Local files     -> ./my_package/module.tri (project-relative)
2. Atlas cache     -> ~/.trident/cache/<os>/my_package/module.tri
3. On-chain query  -> os.<os>.atlas.my_package -> resolve Card -> fetch artifact

Cache invalidation: the compiler compares the cached metadata_hash against the on-chain Card's metadata_hash. A mismatch triggers re-fetch.

5. Atlas Namespace

use os.neptune.atlas.my_skill      // Neptune's on-chain Atlas
use os.ethereum.atlas.my_lib       // Ethereum's on-chain Atlas
use os.solana.atlas.my_program     // Solana's on-chain Atlas

Each OS namespace is independent — separate TSP-2 collections, separate governance.

6. Import / Deploy / Reference

7. CLI Commands

trident registry publish

trident registry publish [options]
  --registry <url>     Atlas server URL
                       (default: $TRIDENT_REGISTRY_URL or http://127.0.0.1:8090)
  --tag <tag>          Tag definitions (repeatable)
  --input <path>       Input .tri file or directory (adds to store first)

Publishes all named definitions from local codebase. Optionally adds .tri files from --input first.

trident registry pull

trident registry pull <name|hash> [options]
  --registry <url>     Atlas server URL

Accepts a content hash (64 hex chars) or a name. Stores locally and binds the name.

trident registry search

trident registry search <query> [options]
  --registry <url>     Atlas server URL
  --type               Search by type signature instead of name
  --tag                Search by tag instead of name

Output per result: short hash, name, signature, verified status, tags.

trident deploy (Atlas integration)

trident deploy <input> [options]
  --target <os>        Target VM or OS (default: triton)
  --profile <profile>  Compilation profile (default: release)
  --registry <url>     Atlas server URL
  --audit              Run verification before deploying
  --dry-run            Show what would be deployed

Accepts a .tri file, project directory, or .deploy/ artifact directory. Compiles to TASM, generates deployment artifact, publishes to Atlas.

8. Wire Protocol

HTTP/1.1 JSON API over plain TCP. Production deployments use a reverse proxy for TLS.

Endpoints

PublishedDefinition (request/response)

{
  "hash":               "64-char hex content hash",
  "source":             "fn source code",
  "module":             "module.path",
  "is_pub":             true,
  "params":             [{"name": "x", "type": "Field"}],
  "return_ty":          "Field",
  "dependencies":       ["<hex hash>"],
  "requires":           ["precondition expression"],
  "ensures":            ["postcondition expression"],
  "name":               "my_function",
  "tags":               ["crypto", "hash"],
  "verified":           false,
  "verification_cert":  null
}

PublishResult

{ "hash": "64-char hex", "created": true, "name_bound": true }

SearchResult (in results array)

{ "name": "fn_name", "hash": "64-char hex", "module": "mod.path",
  "signature": "(Field, Field) -> Field", "verified": true, "tags": ["crypto"] }

PullResult

{ "hash": "64-char hex", "source": "fn source", "module": "mod.path",
  "params": [{"name": "x", "type": "Field"}], "return_ty": "Field",
  "dependencies": ["<hex>"], "requires": ["pre"], "ensures": ["post"] }

Environment

9. OS Configuration

Each OS that supports Atlas declares a [registry] section in target.toml:

[registry]
collection_id = "0x..."
mint_authority = "governance"
resolution = "on-chain"
cache_dir = "~/.trident/cache"

10. Security Model

11. See Also

• Atlas: Why On-Chain Package Management — design rationale
• PLUMB Framework — shared token framework
• TSP-2 — Card Standard — the underlying asset standard
• OS Reference — OS model and registry bindings
• CLI Reference — full command reference
• Standard Library — std.* modules