Request Logs

Honesty Ledger (Provenance Layer): This log records events at the Server-known (Layer A) layer.

ZK Trust Boundary:

• What the server sees: Request timestamps, action types, status codes, latencies, and payload sizes.
• What stays on device: Plaintext payload contents, query parameters, and vector results.

---

Metadata Request Audit Trail

The Requests Log provides a detailed audit trail of all synchronization operations between your local client agents and the replication endpoint. This log is crucial for debugging integration performance and verifying network activity without exposing sensitive memory contents.

Log Schema and Columns

Each request logged contains only metadata properties:

• Time: The exact timestamp of the synchronization event.
• Type: The class of operation executed:
  • ADD: A client-side write replicating a new encrypted memory envelope.
  • SEARCH or GET ALL: Verification and sync-pointer updates.
• Entities: Bound masked reference tags.
• Event Count: The number of envelope units committed or synced.
• Latency: Network transit and database insertion latency in milliseconds.
• Status: Execution state (e.g. OK / Error).

Zero Payload Logging Guarantee

Under a zero-knowledge threat model:

• No Payload Extraction: The replication endpoint does not accept, log, or parse plaintext.
• Encrypted Envelopes: The ADD request body contains only ciphertext bytes.
• Search Metadata: The SEARCH request logs that a query was executed against the database metadata but does not log the search vector or query string.

---

Offline Reference Analogs: This documentation was written with visual and rhythm reference to platform/features/platform-overview.html.