P0: Universal Artifact Identity + Agent Trajectory Bundle v1

[bitmaster162]

Goal

Define the cross-provider identity and portable run-history contracts needed to consolidate ChatGPT Library, Google Drive, GitHub, local/server files and historical AI-agent work without losing provenance.

Baseline binding

Planning baseline observed for ContinuityOS master: 021e2d521efc4df0ce390b38a919bc2f0b675460 / tree 803d89c3e81ea3a83147cd63879a32f8a88c9afe.
Re-read the protected branch before any persistent source write.

Universal Artifact Identity v1

Required fields:

• artifact_id
• source_system
• provider_object_id
• provider_revision_id
• source locator/path
• raw SHA-256
• normalized hash only as derivative metadata
• mime/type/size
• source created/modified time
• observed_at
• custody role
• parent/derived-from lineage
• semantic_family_id

Relations:

• T0 EXACT = same raw bytes/hash
• T1 DERIVED = same logical object, transformed/exported/reformatted
• T2 RELATED = distinct artifacts supporting the same event/decision/project state

Semantic similarity MUST NOT authorize deletion.

Agent Trajectory Bundle v1

Normalize every agent run into:

AGENT_TRAJECTORY_BUNDLE/
  RUN_MANIFEST.json
  INPUT_REFERENCES.json
  ENVIRONMENT.json
  TOOL_EVENTS.jsonl
  MODEL_EVENTS.jsonl
  DECISIONS.jsonl
  OUTPUTS/
  PATCHES/
  SCREENSHOTS/
  RECEIPTS/
  FINAL_RESPONSE.md
  REDACTION_REPORT.json
  MANIFEST.sha256

Required lineage: provider/model/agent/task/project/parent/retry/supersession/input hashes/tool events/files read/changed/Git baseline/output hashes/approvals/effects attempted/performed/cost when available/failure class.

Acceptance

• JSON Schemas
• deterministic validators
• canonical serialization rules
• manifest/hash verification
• round-trip fixture
• redaction fixture
• duplicate/derived/related fixture
• replay fixture
• no implicit truth/authority promotion

Integration boundaries

• ArchiveOS owns exact raw provenance/custody.
• ContinuityOS owns event/replay lineage.
• PostgreSQL may index/query relationships later.
• Library/Drive copies are custody/evidence, not source authority.
• No deletion/move/deploy/runtime/trade effects in this issue.