Summary
The monitor currently returns bool from VerifyEntry() and logs to slog. It needs to produce structured Gemara AuditLog artifacts that can be submitted back through the ingest API.
Context
The monitor is a consumer-edge verification tool. Its verification results (publisher trust, schema validation, reference integrity, DSSE signature verification) need to be durable and machine-readable — not just log lines. Writing AuditLog results back to Tessera via the ingest API makes the verification itself auditable.
Acceptance Criteria
- Define the AuditLog schema for verification results (what was checked, when, what the result was, which log index was verified)
- Monitor produces structured AuditLog artifacts, not just slog output
- AuditLogs are submitted through
POST /api/ingest and stored in Tessera
Relates-to: #194
Summary
The monitor currently returns
boolfromVerifyEntry()and logs to slog. It needs to produce structured Gemara AuditLog artifacts that can be submitted back through the ingest API.Context
The monitor is a consumer-edge verification tool. Its verification results (publisher trust, schema validation, reference integrity, DSSE signature verification) need to be durable and machine-readable — not just log lines. Writing AuditLog results back to Tessera via the ingest API makes the verification itself auditable.
Acceptance Criteria
POST /api/ingestand stored in TesseraRelates-to: #194