Product BriefACTIVE
ASA
Problem: Govern authorized local file actions alongside bounded read-only email triage, without provider-side mailbox mutations.
Operator-controlled resource access and local file workflows, with bounded read-only email triage.
Best Fit
- Controlled Email Intake, Triage, and Draft Preparation: Support leads, operations teams, and coordinators needing categorized inbox triage and suggested drafts with strict human gate approval.
What exists today
- Local filesystem observation, deterministic rules and guarded file moves
- Local move history, recovery primitives and undo
- Read-only email intake and sync
- Message storage and display
- Triage and workflow audit
- Draft reply suggestions
- Ops Console
- Controlled VM email runtime with same-origin API (within bounds)
- Self-hosted resource daemon and documented installation path (within bounds)
- Human-gated operator workflow (within bounds)
Explicitly not included
- Not stable public GA
- No broad rollout or SLA claims
- No provider-side send/delete/archive mailbox mutations
- No autonomous email actions
- No semantic search or AI chat
- Fully offline restart with durable authorized local policy restoration is not yet verified
Evidence (Proof)
Claim Verification
VERIFIED
Operational Proof
BOUNDED
Bounded operational evidence exists for the controlled live VM runtime, same-origin API and repo-side productization evidence.
Last reviewed: 2026-09-28
Deployment Modes
- Controlled VM runtime
- Self-hosted/deployable operator install
Related Technical Reading
Commercial Entry
Status: AVAILABLE_BOUNDED
What to send us:
Request ASA pilot →- Primary business or technical problem
- Current workflow and operator roles
- Data sensitivity and residency policies
- Preferred deployment environment (Self-hosted VM / Docker / On-Prem)
- Model strategy preference (local open-weight vs external API)