Architecture — the control layer.
TVEVT is not a posting tool. It is infrastructure for signal governance and distribution authority: Draft → Governance → Execution Immutable Log. This page defines what the system is, what it enforces, and what “proof” means in v1.
Canonical doctrine
The Signal Journey is the product: drafting discipline, governance gates, and immutable execution proof. Anything that bypasses governance is “noise”, not infrastructure.
Three pillars
- Infrastructure (not UX): control is the product.
- Embedded AI (operational): preparation + policy checks (not “auto-posting”).
- Immutable execution log: proof of what happened, where and when.
1) The Signal Journey
| Surface | What it is | Output |
|---|---|---|
| Drafting | Message creation, tone discipline, channel-ready variants, deterministic formatting rules. | Prepared payload variants |
| Governance | Approvals, policies, role gates, and plan-based controls before anything can be executed. | Authorized release |
| Execution Log | Append-only proof: channel + time + payload + status. No silent edits, no deletions. | Immutable record |
2) What “Governance Console” means
| Control surface | What it enforces |
|---|---|
| Roles & permissions | Owner / Editor / Approver gates. Prevent accidental or unauthorized output. |
| Approvals | Single-step or multi-step approvals (by tier). Nothing goes out without passing gates. |
| Execution rules | Channel constraints, allowed formats, scheduling windows, and policy checks. |
| Retention & proof | Immutable log retention by plan. Auditability becomes a product property. |
| Connectors | Per-channel integration + enforcement. “Can publish” is a permissioned capability. |
3) Limits model (v1)
Limits are not pricing decoration. They are governance boundaries: executions, approvals, retention, connectors, storage, API/webhooks.
Limits that matter
- Executions/mo (append-only log entries)
- AI credits (variant generation / policy checks)
- Approval depth (1-step / 2-step / multi-level)
- Log retention (30d → 7y)
- Connectors (channel integrations)
- API/Webhooks (read → write; enforcement hooks)
- SSO/SCIM and SLA (enterprise governance)