Skip to content

Phase 1 — legal/licence gate and adapter hardening #7

Description

@thebeastagi

Scope (ROADMAP.md, Phase 1)

  • Obtain explicit licences/permissions for any ASTRA-family code reuse before extraction.
  • Replace synthetic-only adapter gate with a trust-tiered adapter registry.
  • Add subprocess isolation and OS-level resource limits for untrusted adapters.
  • Add signed ledger checkpoints or external anchoring.

Owner-task addition (Robin, 2026-07-19): an explicit owner-permission/licence manifest mechanism — no third-party code without a recorded permission entry.

Acceptance checklist

  • Trust-tiered adapter registry replaces the Phase-0 synthetic-only gate (validate_adapter); tiers distinguish synthetic / first-party real-data / untrusted third-party adapters.
  • Subprocess isolation with OS-level resource limits (rlimit CPU/address-space/files, wall-clock timeout) available for untrusted adapters; contained failure on limit violation.
  • Signed ledger checkpoints (HMAC-SHA256, key from environment only, never stored) and/or external anchor export; ledger verifier validates checkpoint continuity.
  • Permission manifest mechanism: machine-readable owner-permission entries; adapters declaring third-party provenance cannot register without a matching entry. Repo ships with zero ASTRA-family permissions (licensing unresolved — clean-room invariant stands).
  • Tests green (ruff + pytest 3.10/3.11/3.12). Docs (README/ROADMAP/ARCHITECTURE) updated truthfully.
  • Invariants: L4 human-gated; no discovery claims; no secrets; $0 spend.

Dependencies

None (first phase after shipped Phase 0).

Tasks

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicPhase epic: groups task issuesphaseRoadmap phase marker

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions