Chapters
DOC-04 / Technical reference
Technical Documentation
The harness of Synedre, in depth. A public, sanitised reference: how the data layer, the agentic core, chantiers, automata, the hub, email, memory, deployment and façades actually fit together.
11 chapters
Anatomy of Shyrka — see the body firstNightly loop
The system maintains its own documentation
Every night, the harness inspects its own state — doc↔code drift, health check, gated regeneration. This terminal shows the actual log of the last session.
Chapters
Overview of the Synedre OS Agentic Harness
This page presents the overall architecture of the harness — its three execution layers (Nuxt, Python, scripts), their organization around the single PostgreSQL database, and the complete lifecycle of a request through to deployment.
Synedre OS data layer
This chapter describes the persistence architecture of the Synedre OS harness: a single PostgreSQL database, three distinct access paths (Nuxt, agentic Python, Drizzle ORM), and the naming conventions that organize the CodeMyShop and Synedre table families.
The Agentic Core: Atlas and the Agents
Describes the architecture of the agentic engine: LLM classification of incoming emails, headless spawning of Claude Code via pseudo-TTY, injection of agent personas, and post-spawn orchestration (deploy, QA, recap).
Worksites, Jobs & Tasks — Data Model and API
Describes the worksite/job/task hierarchy in Synedre OS, the DB data model, canonical statuses/scopes, and the associated Python API.
Automata, scheduling and runs
How the Synedre harness orchestrates CodeMyShop: agents vs automata, scheduling, distributed browsing and the nightly documentation self-maintenance loop.
Hub — Synedre OS Administration Interface
Description of the Nuxt mothership-app, its modular layer architecture and the complete map of /hub/* pages it exposes.
Inbox hub & Atlas Inbox — two email pipelines
Describes the two IMAP→DB pipelines of the harness (contact@ sorted for the hub, atlas@ triggering agentic actions), the outbound sending facade, and the associated blocking doctrines (AV scan, zero direct client contact).
Memory & Learning — Three-Level Architecture
This chapter describes the three memory levels of the Synedre OS harness (reflex, Zettelkasten, vector pgvector), the associated indexing automata, and the loop for capitalizing errors into reusable rules.
Deployment & infrastructure
Describes the Synedre OS release pipeline and its tenants, including the asymmetry between ./deploy (preprod/AI) and ./ship (production, gated by fleet), the YAML dispatcher, the build-host-without-build-VPS pattern, and the doctrines associated with secrets and commits.
Synedre harness automata catalog
How Synedre orchestrates CodeMyShop through agents, task queues, and automatic guardrails, from incoming mail to deployment.
Skills, agents & hooks — Synedre OS agentic harness
This chapter describes the architecture of the synedre-os Claude Code harness: the invocable skills, the delegable sub-agents, and the event hooks that orchestrate the doctrine (guardrails, memory injection, stream-commits).