8 packsschema-valid presetsexecutable policy, not consultingApache-2.0
Constitution Marketplace
Compliance is usually a consulting engagement. EcoCloud productizes it: each pack is a schema-valid EcoCloud Agent Constitution — one-click governance policy for a workspace — plus a map of the live governance kernels that enforce it. Every preset validates against the canonical constitution.schema.json, and every control links to a kernel that exists today. Copy one, extend it, ship it.
Enterprise dispatch — teams + value-thresholds + approval routing
Enterprise Operations
Route high-value or low-confidence requests to a named approver team (e.g. Finance) — composes with team routing, on-call shifts, and the manager hierarchy.
boundary EcoCloud routes the approval to the right human; it does not auto-approve, hold funds, or move money. The constitution is enforced before the action commits; a hard violation (forbidden_terms) still beats the approval gate.
Product & Project Management
Product Delivery Pack
Rank, sequence, and simulate the backlog autonomously; gate every deploy or public post to a human.
Policy GateEvery backlog write (create, reprioritize, assign) passes the workspace constitution gate, which denies anything above max_priority, touching a forbidden tag/assignee, or carrying a forbidden term like 'deploy to production'.
PrioritizationThe agent ranks the backlog with a RICE/WSJF score so reprioritization is an auditable, reproducible ordering rather than an opaque LLM judgment.
SequencingStory-level dependencies are resolved into a task DAG that computes the critical path and per-task float so the agent sequences sprints against true blockers, not guesswork.
Scenario AnalysisBefore committing any scope or date change, the agent runs the what-if scenario matrix and surfaces the resulting risk band to the human owner.
Production Change ControlAny production-affecting action (a deploy ticket transition or a release post) is dry-run first, then held for maker-checker approval before the real write executes.
Public EgressOutbound public posts (changelogs, status updates, social) are audited for content and routed only to allowlisted destinations before egress.
Autonomy RolloutAutonomy expands from suggest-only to act-with-approval to act per the risk-based rollout policy, with override-hotspot analytics flagging where humans keep reversing the agent.
boundary This pack governs, sequences, and stages backlog and release decisions only; it never executes a deploy, merges code, publishes a public post, or moves money — those remain human-approved actions outside the agent's autonomous scope.
Third-party & fraudCounterparty gate — KYA passport status + LEI / IBAN / BIC validation + revocation hotlist before any action touches a counterparty.
Policy GateEvery autonomous write is gated against the constitution, denying any action whose text matches PHI/clinical forbidden terms or that targets a forbidden clinical tag.
AuthorizationConfirm the agent's permissions are scoped to operations objects only, and that its authority never exceeds the human operator who delegated it.
Output ScreeningScreen every generated output through the content auditor and block on any flagged PHI leakage or clinical-advice content before it leaves the agent.
Egress ControlRestrict all outbound destinations to a pre-approved allowlist so patient or operational data cannot be exfiltrated to unsanctioned endpoints.
Attestation & AuditEmit a signed, offline-verifiable Outcome Receipt for each completed operations action and assemble the audit graph into an evidence pack for reviewers.
boundary This pack governs operations workflows only; it does NOT diagnose, prescribe, make clinical decisions, store or move PHI, and it is a policy template that wires governance kernels, not a HIPAA-compliant product, audit, or certification.
Agency / Client Delivery (SOW)
Client Delivery Pack
Govern SOW work: four-eyes before anything client-facing ships, then reconcile billed vs contracted.
Policy gateEvery write is checked against the workspace constitution (priority ceiling, forbidden client-facing/billing terms, objective-tag allowlist, quiet hours) before it reaches a task, document, or client channel.
Four-eyes releaseAny client-facing deliverable, change order, or invoice draft requires maker-checker approval — a second human signs off before it can leave internal scope.
Contracted scopeEach engagement is encoded as a structured SOW (scope, quality rubric, SLA, cost) and evaluated against a signed outcome attestation → fulfilled / breached / unverified plus the earned billing basis.
Billed-vs-contractedBefore a deliverable closes out, the invoice/billed amount is reconciled against the contracted SOW and attested outcome, surfacing exceptions and dispute evidence instead of silently over- or under-billing.
Verifiable handoffOn acceptance the client receives a signed, offline-verifiable Outcome Receipt tying the delivered scope to its attestation, so acceptance can be proven without trusting the agency's systems.
Delivery schedulingMulti-workstream engagements are laid out as a task DAG to compute the CPM critical path and float, so the agent schedules and warns on slippage against the SLA instead of acting blind.
Output controlOutbound drafts pass a content auditor (pass / flag / block) for unsubstantiated claims, confidential leakage, and tone before any client-facing send.
Egress controlClient and external destinations are checked against an egress allowlist so the agent can never send a deliverable or status to an unapproved recipient.
Evidence & lineageThe full audit graph of every approval, attestation, and reconciliation is exported as an evidence pack the client or an auditor can review.
boundary This pack governs, verifies, and attests SOW delivery — it does not move money, issue invoices, or sign legal contracts on the agency's or client's behalf; it computes the billable basis and produces evidence while humans approve releases and a billing system charges.
Sales & RevOps
Pipeline Integrity Pack
Forecast and route deals autonomously; hold discount approval and contract signing for humans.
Policy GateEvery deal write is checked against the workspace constitution before it executes, denying autonomous discount approval, contract signing, and forbidden-term actions.
Signing LimitDiscounts or contract values above the configured signing limit are held in escrow and constrained so the agent never exceeds the authority of its sponsoring human.
Margin IntegrityEvery proposed deal is run through a margin-integrity gate that flags discounts which erode floor margin before they reach a human approver.
ReconciliationInvoices and billing statements are reconciled against the underlying deal and contract terms to surface exceptions and dispute evidence.
boundary This pack governs, gates, and attests Sales & RevOps actions — it does not sign contracts, approve discounts, set prices, or charge, hold, or move any money; those stay with authorized humans and your billing system.
Engineering / Platform Ops
Platform Ops Autonomy Pack
Ramp agent autonomy by risk, gate changes behind eval + A/B, guard egress, four-eyes on prod writes
Policy GateEvery write is gated by the constitution policy, denying actions whose text contains destructive terms (drop table, delete production), out-of-scope tags, or priority above the configured ceiling.
Autonomy RolloutAutonomy is ramped per agent by measured risk band, so new or low-reputation agents start read-only and unlock broader scopes only as their track record clears each threshold.
Authority BoundingThe agent's effective permissions are subset-checked against its sponsoring human's scopes, so it can never act beyond what its owner is authorized to do.
Pre-Change ValidationAny change is dry-run in preflight and run through a what-if scenario matrix to surface its blast radius and risk band before the real write is allowed.
Change Quality GateCode or config changes must pass golden-dataset eval CI and a two-proportion A/B experiment before promotion, blocking regressions and stat-insignificant rollouts.
Four-Eyes ApprovalProd-affecting writes require four-eyes maker-checker sign-off, escalating to an N-role review quorum for the highest-risk changes flagged by the simulation.
Egress GuardAll outbound calls are checked against an egress destination allowlist and screened for prompt-injection so agents cannot exfiltrate data or be steered to unapproved endpoints.
Durable ResumeLong-running jobs are monitored for stalls and resumed from a durable write-ahead-log checkpoint, with a load breaker tripping autonomy on anomalous spikes.
Attestation & AuditEach completed run emits a signed, offline-verifiable outcome receipt and a replayable trajectory, giving regulators and on-call a causal audit trail of what the agent did.
boundary This pack is a policy template that wires governance kernels into the agent execution path; it does not deploy code, manage infrastructure, hold credentials, or replace your CI/CD, IAM, or human change-approval process, and it is not a security certification or compliance guarantee.
Legal / Law-Firm Operations
Legal / Law-Firm Pack
Conflict screening, privilege walls, four-eyes on filings, and billing governance — agents that respect the duty of care.
Intake & conflictsConflict-of-interest screening before any matter or counterparty action — the constitution gate blocks privileged/conflict-pending tags and unverified counterparties.
ConfidentialityPrivilege wall — generated output is screened for privileged/client-confidential content and egress is locked to an approved allowlist before anything leaves the firm.
Docket controlDocket integrity — simulate scope/date changes against the matter’s critical path and dry-run before any deadline-affecting write commits.
Audit & evidenceMatter audit & evidence — a tamper-evident read·check·approve·mutate lineage plus a SOC 2 / bar-ready evidence export and a signed Outcome Receipt per closed action.
boundary This pack governs and proves legal-operations work; it is NOT legal advice and does not practice law, file with courts, waive privilege, or touch a trust account — those remain with a licensed attorney.
What a pack is — and is not. A pack is a policy template that wires deterministic governance kernels into one coherent control set. It is not a regulatory certification, an audit, or a compliance guarantee, and EcoCloud never holds or moves money, prescribes or diagnoses, or executes payments. Presets are a starting point you adapt to your own obligations — see the constitution spec, Operating Regulations, and What's live.