A reference architecture for emotionally-aware business automation.
Developed by Ciprian Ștefan Pleșca (Stefano D'angelo).
Most business automation is stateless and context-blind: the same auto-reply goes to a client who just signed a six-figure contract and to someone asking for a discount. The Sentinel Protocol is an architecture for automation that carries context — urgency, sentiment, the founder's own capacity to make good decisions right now — through every stage of handling a message, a negotiation, or a schedule.
This repository is the engineering specification: architecture documents,
schemas, prompt specifications, and a reference prototype. The original
conceptual whitepaper is preserved in papers/ as the vision
document; docs/ is what an engineer actually implements from.
| Pillar | What it does | Docs |
|---|---|---|
| Cortex | Ingests messages, scores urgency and sentiment, routes by priority | docs/cortex/ |
| Neural Persona | Learns your writing style, drafts responses that sound like you | docs/persona/ |
| Energy Shield | Paces your workload against your own biometric/cognitive capacity | docs/energy/ |
| Negotiation Intelligence | Data-driven pricing and leverage analysis, transparent by design | docs/negotiation/ |
| Sovereign Path | Local-first, layered-anonymization data security | docs/security/, docs/deployment/ |
See docs/philosophy.md for the design principles
behind these five pillars, including the specific places where this
specification is deliberately more conservative than the original
whitepaper, and why.
Message / Event
│
▼
Ingestion (docs/cortex/ingestion.md) — clean, fingerprint, extract metadata
│
▼
Scoring (docs/cortex/scoring.md) — urgency/sentiment/priority
│
▼
Routing (priority tiers, not covert manipulation — see philosophy.md)
│
├─▶ Drafting (docs/persona/) — style-matched response, if applicable
├─▶ Negotiation support (docs/negotiation/) — if commercial context
└─▶ Capacity check (docs/energy/) — is now a good time to surface this?
│
▼
Human review / send (the founder is always the final approver)
Full component and data-flow detail: docs/architecture.md.
Architecture, all five pillars, reference prototype, and a runnable API
service are complete and tested. See ROADMAP.md for what
remains (channel connectors, the /v1/send endpoint, hosted deployment).
| Layer | Status |
|---|---|
| Architecture & design docs | Complete |
JSON schemas (schemas/) |
Complete |
Reference prototype (prototype/) |
Complete, 46 tests passing |
API service (prototype/python/api/) |
Complete (drafting is mask-selection only — see docs/api/endpoints.md) |
| Channel connectors (Gmail/Slack/Calendar) | Documented pattern, implementation pending |
Start at docs/developers/getting-started.md.
Architecture decisions and their rationale: docs/developers/adr/.
docs/ — architecture, philosophy, per-pillar specifications
schemas/ — JSON Schemas for core data structures
prompts/ — versioned prompt specifications (no secret "God Prompt" — see CONTRIBUTING.md)
reference/ — formulas, scoring definitions, terminology
papers/ — original whitepaper and positioning document
examples/ — sample payloads
prototype/ — reference implementation
tests/ — test suite for the prototype
MIT — see LICENSE. The architecture and code are open. The
original whitepaper in papers/ remains separately attributed to the
author as the source vision document.
See CONTRIBUTING.md.