rebrand Scirium docs (Wall-O -> Scirium) + add v1/v2 documentation package
This commit is contained in:
@@ -0,0 +1,38 @@
|
||||
# Scirium Roadmap
|
||||
|
||||
Status: PLANNED
|
||||
Audience: technical and business
|
||||
|
||||
## 1. Version Curve
|
||||
|
||||
| Version | Capability | Autonomy |
|
||||
|---|---|---|
|
||||
| v1 | Grounded, cited Q&A. Read-only retrieval over scoped M365 libraries. No actions. | Zero writes, answer only |
|
||||
| v2 | Risk-tiered actions. Reporting first, then low-risk writes behind propose-approve-audit. | Conditional, human approved |
|
||||
| v3 | Broader autonomous actions by risk tier, deeper connectors, granular per-channel permissions. | Tiered autonomy |
|
||||
| v4 | Multi-connector breadth, analytics, admin self-service at scale. | Mature, governed |
|
||||
|
||||
## 2. What Changes Between Versions
|
||||
|
||||
Later versions add autonomy, not accuracy. v1 is already fully grounded and cited. v2 through v4 add the ability to act, and only within an approved risk tier.
|
||||
|
||||
| Version | Adds | Does not change |
|
||||
|---|---|---|
|
||||
| v1 | Cited Q&A | Grounding, scoping, isolation |
|
||||
| v2 | Reporting and low-risk writes | Grounding rails, approval gate |
|
||||
| v3 | More connectors and tiers | One channel one domain invariant |
|
||||
| v4 | Analytics and self-service | Hard scope (no PHI) |
|
||||
|
||||
## 3. The Permanent Gate
|
||||
|
||||
The propose-approve-audit gate is permanent across all versions. Later versions add autonomy but never remove or bypass this gate.
|
||||
|
||||
1. Propose: the agent shows exactly what it would do.
|
||||
2. Approve: a human approves or rejects. Nothing executes without approval.
|
||||
3. Audit: the narrow, approved write executes and is logged.
|
||||
|
||||
No version of Scirium becomes a free-roaming agent. Autonomy expands by risk tier, and the gate stays.
|
||||
|
||||
## 4. Hard Scope, All Versions
|
||||
|
||||
Internal staff documentation only. No patient records, no PHI, no HIPAA scope, no medical or vision AI. This boundary is not on the roadmap; it is permanent.
|
||||
Reference in New Issue
Block a user