Blocpod system /
IssuerOS: governed investor communications where 17 agents recommend and humans decide
A multi-tenant operating system for creating, verifying, approving and launching investor-facing communications. Source to claim to content to approval to release, with a hash-chained audit log per organization.
- Governed agents
- 17recommend only; barred from protected actions
- Audit log
- Hash-chainedappend-only, per organization, plus a platform chain
- Lifecycle steps under governance
- 11source → claim → content → workflow → build → QA → approval → release → deployment → monitoring → audit
Bottleneck
Investor communications are a document workflow with legal consequences. Every claim on a page has to trace to a source, every change has to be approved by someone accountable, and a launch has to be reversible. In most companies that lifecycle lives in email threads, shared drives and one or two people who remember which version was signed off.
System
IssuerOS is a multi-tenant platform that connects the whole lifecycle in one governed chain: source, claim, content, workflow, build, QA, approval, release, deployment, monitoring, audit. Its modules map to the work: Control (multi-company command center), Truth (source provenance, verified claims, contradiction management), Flow (requests, tasks, approvals, gates), Factory (AI-assisted production with staging-only authority), Assurance (quality, accessibility, launch readiness, rollback) and Intelligence (the agents).
It is a separate commercial product derived from the VendorGroup Intelligence architecture. It is not a rebrand.
Control
- Recommendation is not action. The 17 agents draft, compare, flag and propose. Protected actions are barred to them in code.
- Approvals are records. Approver, role, evidence and revocation state are stored and correlated with the audit chain.
- Production isolation. The service that builds sites cannot touch production or its credentials.
- Honest integrations. Live-capable adapters (SEC/EDGAR, GitHub) are distinguished from mocks in the interface.
Result
A document workflow that used to depend on institutional memory and inbox archaeology becomes a chain of verified claims and recorded decisions. The result that matters to a buyer is not throughput: it is that every public claim can be traced back to a source and forward to the person who approved it.
Evidence
Where these claims come from.
- Repository README v0.9.0 and CI ↗proprietary licence; architecture and module list public in the README