EcoCloud is an AI-native, agent-operable task workspace. People (and their AI assistants) describe work in plain English; EcoCloud routes it, governs it, and executes it — with scoped keys, a tamper-evident audit trail, and a human in the loop for anything risky. Not a task board with AI sprinkled on top — an operating layer for humans and agents working together.
Every highlighted stage is a zero-dependency, isomorphic kernel — same logic runs in your browser and on the edge. All open-source, Apache-2.0.
Not a concept — the real workspace. Plain-English dispatch, a governed cockpit, and every action signed.
Type a sentence; EcoCloud extracts the task, owner, deadline and priority and routes it — instantly, on-device for the simple cases, with a model for the rest.
Any assistant or autonomous agent reads the discovery manifest and binds natively — scoped fdk_ keys, rate-limited and audited, 48+ governed signed tools.
Open work auto-triaged into Do now · Waiting on you · Blocked · Can slip, with a one-line plan and Team Capacity — who's overloaded, at a glance. All from your live tasks.
Every time you reassign a tagged task, EcoCloud remembers it — and auto-routes the next one to the right person. Deterministic, never overrides what you specify.
Completed governed work closes with an ES256-signed receipt — intent → action → verified result — checkable by anyone, offline, with no need to trust our database.
Per-agent rules, attribute-based micro-roles, confidence thresholds, an approval queue, and a one-switch pause over every autonomous action.
BYOK policy engine: hard-filters by health, capability and privacy level, then scores by cost and latency — returns ranked provider + signed attestation. Falls closed.
Protobuf-style field validation for every MCP tool/call argument: type, required, enum, bounds, format, nullable — per-field typed errors, signed attestation.
People, tasks, decisions and connected systems become a temporal knowledge graph — query what the team knew on any date, and who asserted it.
Define multi-step work with dependencies, retries and human gates; the engine runs it and records every transition for replay.
EcoCloud reasons over the work graph — surfacing the real delay drivers (blockers, stale work, throughput) with recommendations, from data.
The flow is built — an agent calls start_checkout, the human pays on Stripe's hosted page, a signed webhook writes the subscription row. Self-serve checkout activates once billing keys are configured (tracked on /whats-live).
These five are the flagship of a 40+ skill governance library spanning six phases — authorize, measure, clear · settle · verify, identity & trust, lifecycle, audit & dispute. Run any of them live in your browser from the Trust Layer.
Each kernel returns an ES256-signed attestation (kid: flowdesk-envelopes-2026) verifiable against the published JWKS — without trusting the database. Apache-2.0. Run them in your browser at /route-kernel/ and /mcp-schema/.
start_checkout with the user's email — no payment data enters EcoCloudcheckout.session.completed firesEveryone ships a chat box. Very few ship memory, permissions, action execution and accountability — the things an agent needs to be a coworker, not a toy.
Scoped keys, a workspace constitution, approval gates and a kill-switch ship in the core — so you can let agents act without betting the company on it.
A SHA-256 hash-chained, ECDSA-signed Merkle audit ledger makes every action tamper-evident. Your compliance story is "here's the cryptographic chain," not "trust our logs."
The governance logic — constitution, injection screen, authz, AI routing, MCP contract validation — ships as zero-dependency, Apache-2.0 code runnable in any browser or edge environment. Vendor lock-in on governance logic is a category-level risk. Ours is open.
Bring your own model key so inference runs on your account; the Route Kernel picks the right provider by your own cost and privacy policy. Export or delete your data anytime.
The billing path is built and HMAC-webhook-verified — start_checkout returns a Stripe URL, the human pays, a verified webhook upgrades the account. Self-serve checkout is planned: it goes live once Stripe keys are configured.
Minutes from sign-up to your first closed task. A 40+ skill governance library, signed outcome receipts, 48+ governed MCP tools.