Technical resources.
The brief, the architecture, and the questions security and finance teams ask first.
The foundational thesis and framing — integrated memory and governed execution for autonomous AI systems.
Read the brief →The governing model — signed actor identity, execution envelopes, admission boundaries, and evidence structures.
View architecture →Operator View
View Full Edit
Evidence report for the Alder & Vale demo episode. This export captures the transcript ingest, knowledge recall set, recorded decisions, outbound actions, storage receipts, and point-in-time bundle metadata for episode ep-2847.
| # | Record ID | Category | Tier | Actor | Time | Content |
|---|---|---|---|---|---|---|
| 1 | ingest_a1f3 | Ingest | hot | Ingress Relay | 14:13:05 | Zoom transcript received for Q3 Partnership close review. 47 minutes, 6,214 words, source verified against meeting receipt. |
| 2 | recall_0e82 | Recall | hot | Research Analyst | 14:13:34 | Knowledge bank query 1/14 returned prior mandate scope and industrials expansion constraints. |
| 3 | recall_1c49 | Recall | hot | Research Analyst | 14:13:49 | Knowledge bank query 2/14 surfaced portfolio performance note and three flagged positions. |
| 4 | recall_2d17 | Recall | hot | Research Analyst | 14:14:02 | Knowledge bank query 3/14 surfaced Nov 1 EU data residency deadline tied to Renata Solis review. |
| 5 | recall_3b55 | Recall | hot | Research Analyst | 14:14:19 | Knowledge bank query 4/14 confirmed EU hosting requirement before Q4 close for client data. |
| 6 | recall_4a2e | Recall | hot | Research Analyst | 14:14:31 | Knowledge bank query 5/14 captured industrials coverage expansion scope and effective quarter. |
| 7 | recall_5f91 | Recall | hot | Research Analyst | 14:14:46 | Knowledge bank query 6/14 pulled the MNPI boundary review note for pre-announcement financial material. |
| 8 | recall_6c30 | Recall | hot | Research Analyst | 14:15:00 | Knowledge bank query 7/14 verified disclosure alignment across actor scopes for outbound communication. |
| 9 | recall_7d84 | Recall | hot | Research Analyst | 14:15:15 | Knowledge bank query 8/14 returned commercial terms and fee structure notes for expanded mandate. |
| 10 | recall_8e62 | Recall | hot | Research Analyst | 14:15:31 | Knowledge bank query 9/14 logged action item to deliver data migration plan by Oct 15. |
| 11 | recall_9a07 | Recall | hot | Research Analyst | 14:15:44 | Knowledge bank query 10/14 logged revised SLA draft follow-up for Renata Solis. |
| 12 | recall_a1b3 | Recall | hot | Research Analyst | 14:15:57 | Knowledge bank query 11/14 logged compliance review scheduling requirement with legal. |
| 13 | recall_b2c9 | Recall | hot | Research Analyst | 14:16:11 | Knowledge bank query 12/14 confirmed Nov 3 follow-up call and partner attendance expectation. |
| 14 | recall_c3d1 | Recall | hot | Research Analyst | 14:16:23 | Knowledge bank query 13/14 extracted commitments summary with four items and two deadlines. |
| 15 | recall_d4e5 | Recall | hot | Research Analyst | 14:16:39 | Knowledge bank query 14/14 completed synthesis handoff to Partnership Close for outbound preparation. |
| 16 | decision_g1h | Decision | warm | System | 14:18:02 | Recorded decision: all client data must be EU-hosted by Nov 1. Owner assigned to engineering. |
| 17 | decision_g2i | Decision | warm | Partnership Close | 14:18:27 | Recorded decision: revised SLA draft to Renata Solis due Oct 20 with high priority. |
| 18 | decision_g3j | Decision | warm | System | 14:18:49 | Recorded decision: legal compliance review required before mandate expansion language is reused. |
| 19 | decision_g4k | Decision | warm | Outreach Operator | 14:19:06 | Recorded decision: Nov 3 follow-up call confirmed with agenda for migration status and SLA review. |
| 20 | action_h1l2 | Action | hot | Partnership Close | 14:20:11 | Action receipt: follow-up email drafted and sent to Renata Solis with three action items and policy check pass. |
| 21 | action_h2m3 | Action | warm | Outreach Operator | 14:20:44 | Action receipt: two calendar holds created for Nov 3 follow-up and data migration review. |
FAQ
Questions Teams Ask Before Deploying Consequential AI
What is Synaptik Core?
We're building infrastructure that prevents autonomous systems from committing unauthorized changes to systems of record by requiring cryptographic proof of authority before the write occurs. AI is not required — the same admission chain governs agents, scripts, integrations, and humans-in-the-loop.
How is this different from audit logs?
Logs record what happened after a write. Synaptik gates the write on a sealed authority chain — the proof exists before the action becomes real.
How is this different from human-in-the-loop?
HITL captures a click. Synaptik governs what the AI evaluated before the human, whether the approver had standing, and blocks the write until a valid commit receipt exists.
How is this different from AI governance?
AI governance manages models out-of-band — usage policies, risk reviews, documentation. Synaptik Core operates in-band: authorization at the commit boundary, enforced before any system — agent, script, or integration — writes to a system of record. AI made the problem urgent; it didn't create it.
Is Synaptik Core only for LLM-based systems?
No. Synaptik is source-universal — the model is one participant, not a requirement. The system governs reasoning from deterministic sources (Python scripts, notebooks, SQL queries), human-in-the-loop inputs (manual overrides, policy approvals, expert observations), and external sensors (real-time data feeds and API webhooks). Each is passed through the same governed admission chain: execution context recorded, policy checked, memory committed or refused, evidence sealed.
Do you store our data?
No. Synaptik governs execution and seals evidence; it does not take custody of your records. Your data stays yours.
How is data kept secure?
Your data is encrypted at rest and in transit. Only you can access it. Each user gets their own isolated workspace with secure authentication. Every action creates a tamper-proof audit trail that can’t be altered or deleted, giving you complete visibility and control over your data.
Where does it run?
Local-first. Scoped workspaces run in your environment. Hosted and on-prem options exist for teams that need them.
Can Synaptik Core run offline?
Yes. Synaptik Core is designed to work completely offline. No internet connection required. All memory operations and policy enforcement happen locally on your infrastructure, which is critical for air-gapped environments, regulated industries, and edge computing scenarios where connectivity isn’t guaranteed.
What compliance certifications is Synaptik working toward?
SOC 2 Type I and Type II are the near-term targets. FedRAMP Ready is on the longer-horizon roadmap for government and defense deployments. HIPAA-compliant deployment is available for regulated healthcare environments through institutional engagement. See the Roadmap for current status.
Have a deeper question?
Bring it to a working session with the team.
Policy admission boundary
Every input checked before it enters governed state
Decision lineage
Every decision attributed, linked, and reproducible
First-class evidence
Every action exportable with full proof chain