Clear Frameworks owner control
One login. One CFW control panel.
EVE will handle approved work backstage. You will see customer needs, decisions, verified outputs, tools, and exceptions that require the owner.
Safe local candidate
Owner access is production-disabled.
The dedicated Clear Frameworks identity project is bound. Admin remains disabled until owner activation, recovery, and AAL2 isolation have hosted proof.
Owner sign-in
Open Clear Frameworks Control
Use an invited owner account. Customer and Retehost accounts cannot open this view.
Owner security
One more proof
Select a verified authenticator and enter its current six-digit code.
No verified authenticator is available. Enroll an authenticator now. The QR code is created by the dedicated Clear Frameworks identity project and is never sent to Retehost.
Scan this QR code with your authenticator app. Then enter the newest six-digit code. The enrollment stays unverified and cannot open Control until that code succeeds.
Access stopped safely
This account is not a current Clear Frameworks owner.
No admin records were requested. You can return to the customer portal without creating another login.
Open customer portal
Clear Frameworks
/
Owner Control
Production
Owner · AAL2 required
Clear Frameworks / All CFW / Candidate
Owner overview
Auto-select lets the harness choose the narrowest qualified operating profile. Profiles never grant authority.
Owner overview
Only what needs you.
Customer needs, owner decisions, verified outputs, and exceptions rise here. AI work stays backstage.
EVE
Give the outcome, not the steps.
When connected, EVE will route the work, select bounded specialists, run independent checks, and return only decisions and verified results.
Current boundary
Connection status
- Identity & dataDedicated CFW project bound; activation locked
- EVE & toolsNo runtime or effects connected
- OwnershipClear Frameworks controls product and data
CRM
Customer relationships and pipeline.
Review every inbound request, keep the next action visible, and move qualified work through one accountable record.
Private CRM state cleared
Today
What needs attention.
Review new demand, protect follow-up, and open the record that needs the next decision.
CRM data unavailable
The CRM snapshot could not be loaded. Counts below are last known or unavailable.
Attention queue
Next decisions and follow-up.
Source coverage
What this CRM can see.
- Email and Voice forwards
- Unknown
- Sent-mail history
- Unavailable
- Manual activity
- Unavailable in Stage 1
Inbound source status hidden
Inbound source
Business inbox
CRM data is hidden until current owner+AAL2 access is verified.
Google Voice texts, missed calls, and voicemail arrive only when forwarded to this mailbox. Spam and Trash are excluded before import.
CRM data unavailable
The CRM snapshot could not be loaded.
Choose a request
Select an item from the queue to review its source, safe message text, and next action.
- Source
- —
- Received
- —
- Match
- —
- Provenance
- —
No request selected.
Platform profiles
Who signed up, and where.
Every profile is tied to the CFW platform the person selected. Returning users appear once per platform.
| Person | Platform | Status | Signed up | Source |
|---|
No platform profiles have been recorded yet.
Leads
Qualified demand with a next action.
Stage 1 exposes the verified lead count; lead records remain unavailable until their server projection is activated.
Lead records are unavailable in Stage 1. The Overview count is the only live lead projection.
| Lead | Status | Owner | Next action | Potential |
|---|
Pipeline
Work moving toward a decision.
Pipeline records remain unavailable until their authoritative Stage 1 projection is activated.
Customers
People and organizations with active history.
A CRM customer is not automatically a portal account, membership, or project.
Tasks
Follow-up that cannot disappear.
CRM task records are separate from project records waiting on a customer.
Activity
An auditable customer timeline.
Inbound evidence, human decisions, tasks, and stage changes remain reconstructable.
More
Connected business records.
These surfaces stay unavailable until an authoritative adapter exists.
Projects
Winning an opportunity creates no project automatically. A separate approved link or create action is required.
Estimates and invoices
No authoritative estimate, invoice, balance, or payment source has been connected.
Communication history
Sent-mail history and response-time reporting stay unavailable until a real outbound evidence source is approved.
Import and export
Bulk import, export, merge, and destructive actions remain disabled until the server policy gate is complete.
EVAN
Your chats load after sign-in.
What can I help with?
Ask a question or tell me what you want to do.
Response details
- State
- idle
- Model used
- Not recorded
- Run ID
- —
- Receipt
- —
Owner-scoped work context
Projects, roots, tasks, proof, and memory.
This surface shows only server-projected CFW records. Missing adapters stay visibly waiting; it never invents folders, files, tasks, history, or memory.
Waiting for the current CFW owner session and server projections.
Current evidence
Active work
Connect to load owner-scoped work records. No agent connection is assumed.
Saved work
History
Saved chat and task evidence are different records. Open a conversation in Command; inspect task results in Workspace.
Waiting for verified owner records.
Persistent owner memory
What EVAN remembers
Review and save your preferences in the existing EVAN memory store. Identity stays fixed; memory does not grant authority.
Connect to read the current saved memory revision.
Edit owner memory
One item per line. Save is explicit. Conflicting edits require you to review the current version; work closeout is not automatically written into this profile.
Load your current memory before editing.
Project memory
Bind content to an existing proposal, then retrieve committed records with their receipts. Personal preferences above remain separate.
Project memory setup and owner decisions
Load the current owner-scoped records before making an explicit namespace, binding, or proposal decision. A displayed record is not a grant of authority.
Waiting for verified owner scope. No project-memory operation has run.
Bounded role profile template
A role profile narrows how work is approached. It cannot carry credentials, commands, provider settings, or authority.
Download example JSONReceipts, not promises
Work proof
A completed model run, a verified external action, and a retrievable memory update are separate claims. This view shows only the evidence available.
No verified run receipt loaded in this session.
Company data
The CFW system of record.
Products, customer editions, sites, licenses, and deployments live here—not on the owner’s front page.
Authenticated CFW registry
Tools and service evidence.
Tool availability uses the current owner-authorized records. The private entity directory requires a protected read API; it is not included in this page’s public assets.
active
waiting
Signed-in CFW identity
Audited rolesDerived only from the current server-proven owner session and AAL2. Effects still use audited owner controls.
CFW identity handoffAvailable after the current CFW owner session and AAL2 are verified.
EVE components
Working parts stay active. Anything not proven ready stays waiting.
Private entity directoryNot loaded
Tools registered
Sites & apps are not connected.
Each product runtime will open from here with its own identity, portal, release state, and customer boundary.
CFW license authority is available in Capabilities.
The owner+AAL2 projection shows base-tool licenses, separate EVE and EVAN licenses, named seats, exact builds, per-tool access, delegations, and append-only revocations. Retehost remains hosting enforcement only.
Deployment records are not connected.
This will show approved live versions, exact predecessors, release receipts, and rollback points—not a direct deploy button.
People & access
Identity belongs to each CFW product.
Users, invitations, app access, roles, MFA, recovery, and sessions appear only after exact server authorization.
User directory is locked.
No user list is loaded in this candidate. Customer and Retehost identities cannot grant CFW owner access.
Invitations are not connected.
Future invitations will name one CFW app, role, account, expiration, and inviter. A hosting account or email address alone cannot create access.
Per-app access is not projected.
This will show which CFW product each identity can enter without exposing passwords, factors, tokens, or another product's customer records.
Access control is server-authoritative.
Browser labels, email matches, role JSON, and hosting accounts never grant owner authority.
MFA setup and recovery remain separately gated.
Password recovery cannot remove MFA, change a role, accept a license, or grant owner access. Verified factor state will appear here only after backend authorization.
Open password recoverySession management is not connected.
Owner actions will require a current non-anonymous session and AAL2 revalidation.
Files & assets
Approved content and delivery evidence.
Browse bounded files by purpose. Private source and customer delivery authority remain separate.
No file store is connected.
No private file can be listed, downloaded, released, or delivered from this candidate.
No release manifest is projected.
Approved artifacts will be bound to exact source and output digests.
No asset library is connected.
Public, customer-safe, and private assets will remain explicitly classified.
No delivery authority exists here.
A file approval is not a download, dispatch, provider action, or customer receipt.
Automations
Bounded capabilities EVE can use.
Approved procedures, active runs, schedules, and stop controls remain narrow, versioned, and independently checked.
No automation run is active.
When connected, this shows the requested outcome, current bounded step, stop state, and verified result—not background chatter.
PC approvals are shown with their exact queued task.
Sensitive or destructive work remains queued until an owner-AAL2 decision is recorded in the Capabilities view.
No scheduled automation is active.
Nothing can run merely because time passed. Current authority is rechecked at execution time.
Use the exact license, grant, device, or file-root revoke control.
Each revocation is append-only and must cancel matching active Harness work without broadening any other capability.
Live activity
What is changing now.
A calm event surface for new customer needs, active work, and important state changes.
Live inbox is not connected.
No message, customer event, or background agent signal is being streamed.
No active-work projection is connected.
Routine AI progress will stay collapsed unless it becomes an exception.
No event stream is connected.
Only bounded, redacted business events will be visible here.
Decision center
Only decisions that need you.
AI preparation and routine work stay backstage. Exact impact and rollback appear before approval.
The current backend does not expose owner decision records. Customer records waiting on a response remain in CRM and are never mislabeled as your decision.
Decision records are not projected yet.
EVE will not ask for approval until an exact target, effect, customer impact, and rollback are available.
No advisor findings are projected.
Security, performance, business, and policy findings will be ranked by severity and routed to the exact owning surface.
No safety review is active.
Overwatch evidence will remain separate from the agent requesting an effect.
Health
Can CFW operate safely?
Service status, failures, and capacity belong here. Healthy machinery stays quiet.
CFW identity
Dedicated project bound. Shared Retehost identity remains prohibited; activation is locked.
EVE runtime
Private harness connection is not active.
Ownership boundary
CFW remains software, data, and license authority.
Production
Promotion remains locked pending hosted proof.
Application health is not connected.
Each CFW product will report its current release, availability, and verified rollback point.
AI runtime health is not connected.
Model activity, agent traces, and token noise will remain hidden unless there is a cost, failure, or owner decision.
Retehost runtime health is not connected.
Hosting status cannot grant CFW product, data, license, or owner authority.
Audit log
Proof behind the summary.
Verified records stay authoritative; AI memory and chat never become the source of truth.
Every approved direction, role version, approval, tool call, verifier result, and output receives a stable record.
Detailed evidence stays here instead of crowding the owner screen.
Derived views rebuild from immutable evidence and verify themselves.
Owner queue projection
Unclassified action records
The backend does not yet prove whether each action is a customer need, owner decision, or another exception, so these records stay neutral.
No open owner-action records.
When connected, only the bounded owner-action projection is counted here.
The EVE record service is not connected.
No run history or AI memory is fabricated in this local candidate.
No output ledger is connected.
Chat text, agent activity, and unverified drafts are never presented as finished work.
No approval ledger is connected.
Future approvals will bind one exact target, effect, actor, predecessor, and rollback.
No incident projection is connected.
Failures that need owner attention will be bounded, redacted, and linked to recovery evidence.
Tools & connections
Your base toolkit and launch status.
Reusable Clear Frameworks tools stay visible here, but each launch remains disabled until the current owner snapshot proves an active CFW license and an exact HTTPS Retehost route. Customer editions and branded backends never appear.
No tools match this view.
Clear the search or choose another category.
Your base tools
Reusable Clear Frameworks utilities and owned tools—not customer editions.
Base modules
Reusable building blocks from your toolkit. No customer backend is projected here.
Connections
Connection records never expose credentials or grant provider authority.
CFW settings
Configuration and boundaries.
Low-frequency technical detail stays here unless it creates an owner decision.
CFW identity
Dedicated project bound; production activation locked.
Production state
Candidate only; no provider or customer effect.
Clear Frameworks is the authority.
Software, source, products, variants, builds, customer data, operating profiles, and licenses remain CFW-owned. Retehost supplies private runtime hosting only.
EVE profiles
Versioned role JSON
Imported profiles are validated and remain session-only candidates. They narrow behavior but cannot grant authority.
Private runtime hosting by Retehost.
Hosting metadata and deployment health can be shown here. They cannot become CFW owner, product, customer, or licensing authority.