Files
0pt/packages/schemas/0pt.lineage_event.schema.json
T
Claude (SIAX platform session)andClaude Opus 5 bcf285f057
CI (SIAX Cloud) / quality (push) Successful in 38s
CI (SIAX Cloud) / security (push) Successful in 17s
merge: unify GitHub main into Gitea main (0pt)
Merges github/main (6 commits: 17-bug audit fix, CI quality gate,
.env.example + .gitignore fix, missing platform clients + registry
services, docs accuracy overhaul) into gitea/main (8 commits: Iceberg
write boundary + live ST0RE verification, lakehouse mapping routes,
Waves 1-4 foundational hardening).

16 conflicts. Both sides had independently written the four
src/clients/*.ts and the two registry services, so those are combined
rather than picked:

- st0re-client.ts: GitHub's endpoint wins on evidence. POST goes to
  /v1/st0re/artifacts/register, not /v1/st0re/artifacts -- verified in
  sax3l/st0re src/api/routes/artifacts.ts, where the bare path is a
  GET-only list route. Gitea's URL normalisation, error-body text and
  mock kept.
- n0d-client.ts: field is `status`, not `state`, with N0D's real 13-state
  union -- verified in sax3l/n0d packages/schemas/n0d.job.schema.json,
  which says explicitly not to add "succeeded". Gitea's mock echo,
  URL normalisation and error-body text kept.
- cl0ud-client.ts: Gitea's fail-closed HTTP normalisation kept (a 200
  with no `decision` reads as "deny", not as a silent allow). GitHub's
  PolicyDecision/PolicyDecisionValue naming kept; PolicyResult retained
  as an alias.
- aud0-client.ts: permissive union of both input types (optional
  payload/metadata/correlation_id), GitHub's echo return, Gitea's URL
  normalisation and error-body text, plus a JSON-parse fallback so a
  successful POST with an empty body does not throw.
- dataset-service.ts / source-service.ts: GitHub's record/DTO split and
  event naming (0pt.source_created / 0pt.create_source, which the merged
  docs already reference) plus Gitea's name validation, description /
  created_by fields and actor_id derivation. List filters are the union.
- lakehouse mapping routes: GitHub's shared lakehouse-mapping-registry
  singletons (without which every write 400'd "mapping not found") AND
  Gitea's Zod parseBody validation. Both, not either.
- src/types/source.ts, src/types/dataset.ts: unions of both vocabularies;
  GitHub's `access` legal-sourcing field kept.
- .env.example: GitHub's audited inventory plus Gitea's Zitadel /
  AUTH_ENFORCE block.
- CLAUDE.md, docs/ICEBERG_WRITE_BOUNDARY.md: GitHub's corrections kept,
  Gitea's live-verification kept and marked as superseding the
  "would 400 outright" finding (Gitea had already added the required
  X-Tenant-Id/X-Actor-Id headers).
- pnpm-lock.yaml: regenerated with pnpm 9.15.9, not merged.

Also corrects CLAUDE.md's claim that the banned services/scrapers stack
was "since removed" -- the removal PR is open, not merged, and this
branch inherits that code from Gitea main. Nothing here resurrects,
extends or re-wires any of it; services/scrapers/ is byte-identical to
Gitea main.

Verified on the merged tree: typecheck (src/ + tests/) clean;
17 test files, 121 passed, 1 skipped (the realinfra test skipping
honestly on ST0RE HTTP 401), 0 failures. Gitea main baseline was the
same 121/1; GitHub main baseline could not even `pnpm install`
("packages field missing or empty") -- Gitea's pnpm-workspace.yaml fix
resolves that. Whole-repo `typecheck:app` reports 9 errors, an identical
set to Gitea main's baseline, so it is advisory in both CI workflows
rather than deleted. Lint: 16 problems, identical to Gitea baseline.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-28 12:38:01 +02:00

58 lines
2.9 KiB
JSON

{
"$id": "0pt.lineage_event.schema.v1",
"description": "CONTRACT-ONLY -- 0pt's real lineage emissions today go through Aud0Client.ingestLineageEvent (src/clients/aud0-client.ts), whose Aud0LineageEvent shape is source_type/source_id -> target_type/target_id, not input_assets/output_assets. This wider multi-asset shape exists so tests/p0/enterprise-data-os-expansion.test.ts's contract assertions (from an earlier 'PROMPT 2' pass) have a real file to check; it documents an intended future generalization (multi-input/multi-output lineage), not a built/wired capability. NOTE (GitHub<->Gitea unification merge): the two remotes disagreed on `producer` -- one modelled it as an object {app_id, capability_id}, the other as a string plus flat top-level app_id/capability_id. The structured object is kept as canonical here because it names both parts unambiguously; `event_type`, `app_id` and `capability_id` are retained as optional top-level properties so the flat draft's fields are not lost. Nothing in this repo reads or validates against this file, so neither choice changes behaviour.",
"type": "object",
"required": [
"lineage_event_id",
"tenant_id",
"project_id",
"producer",
"input_assets",
"output_assets",
"created_at"
],
"properties": {
"lineage_event_id": { "type": "string" },
"tenant_id": { "type": "string" },
"project_id": { "type": "string" },
"event_type": { "type": "string", "description": "e.g. 0pt.lineage_emitted. From the flat draft; optional." },
"app_id": { "type": "string", "description": "Flat-draft alternative to producer.app_id; optional." },
"capability_id": { "type": "string", "description": "Flat-draft alternative to producer.capability_id; optional." },
"producer": {
"type": "object",
"description": "The capability/app that produced this lineage edge.",
"required": ["app_id", "capability_id"],
"properties": {
"app_id": { "type": "string" },
"capability_id": { "type": "string" }
}
},
"input_assets": {
"type": "array",
"items": {
"type": "object",
"required": ["asset_type", "asset_id"],
"properties": {
"asset_type": { "type": "string", "enum": ["dataset", "iceberg_table", "artifact", "source", "document", "signal"] },
"asset_id": { "type": "string" }
}
}
},
"output_assets": {
"type": "array",
"items": {
"type": "object",
"required": ["asset_type", "asset_id"],
"properties": {
"asset_type": { "type": "string", "enum": ["dataset", "iceberg_table", "artifact", "source", "document", "signal"] },
"asset_id": { "type": "string" }
}
}
},
"st0re_artifacts": { "type": "array", "items": { "type": "string" } },
"quality_report_id": { "type": "string" },
"correlation_id": { "type": "string" },
"created_at": { "type": "string" }
}
}