Owner
Platform AdminUnified operating platform
Deal Manager
Data Sync
Control mappings, sync jobs, outbox events and adapter data movement.
Core records
4Permission gates
1Sync controls
Readiness gates
Source smoke, reconciliation, audit, cleanup, package and write-candidate gates in one operator view.
Tracked gates
7Disabled gates
...Control actions
DisabledGate status
Blocked by default
Localhost adapter coverage
Surface-to-adapter proof
Checks every visible Localhost surface against Core objects, source maps, command drafts, adapter readiness and closed gates.
Surfaces
...Live bound
...Command-bound
...Read-model bound
...Needs binding
...Source maps
...Surface coverage
Every main Localhost route must be tied to an adapter, Core model, command model or gated shell.
Source smoke evidence
Bounded read-only probes
Project, CRM, ERP and Files endpoint evidence from the approved read-only inspection window.
Modules
...Endpoint reviews
...Bounded smokes
...Runtime calls observed
...Write adapters
...Evidence modules
Module coverage
Connected workspace coverage
Module surfaces, settings parity and governed action staging through the current approval boundary.
Coverage
...Modules
...Panels
...Write adapters
0Approval
...Module coverage
Workspace coverage
Operational module coverage
Coverage for CRM, Files, ERP, Analytics and Loans, followed by cross-module QA and handover.
Coverage
...Modules
...Closeout
...Writes
0Next review
Approval reviewModule deepening
Role tool function matrix
Role capability matrix
Role-scoped coverage for every tool surface and function family before controlled Dev writes or sync are opened.
Roles
...Tools
...Families
...Entitlements
...Capabilities
...Departments
...Missing keys
...Role coverage
Tool entitlements are scoped by role, surface and current execution mode.
Controlled Dev write models
Controlled command model
CRAYS Core command envelopes before any tool apply, sync apply, upload, external send, finance action, bank action or release gate is opened.
Command models
...Model ready
...Apply ready
...Blocked apply
...Exact gate
...Command runway
Model-ready CRAYS Core commands. Tool apply remains blocked.
Core command persistence
Command persistence
Product-Fit checked CRAYS Core command store and guarded command staging before any external apply gate opens.
Schema
...Tables
...RLS gaps
...Rows returned
0Tool apply
OffGuarded command routes
Routes stage CRAYS Core commands only; apply and external side effects stay closed.
Project work item
/api/crays/core-command/project-work-item
Confirmation: stage-project-work-item-command
CRM activity
/api/crays/core-command/crm-activity
Confirmation: stage-crm-activity-command
Files package
/api/crays/core-command/files-package
Confirmation: stage-files-package-command
ERP finance
/api/crays/core-command/erp-finance
Confirmation: stage-erp-finance-command
Loans checklist
/api/crays/core-command/loans-checklist
Confirmation: stage-loans-checklist-command
Sync preview
/api/crays/core-command/sync-preview
Confirmation: stage-sync-preview-command
Product-Fit Check
This command store exists only when it serves the full CRAYS journey and keeps gates closed.
Pilot Workflow charter
Pilot workflow charter
End-to-end pilot scope across property, evidence, economics, Candidate intent, bank package readiness and opening handoff.
Phases
10Roles
11Surfaces
15QA evidence
5Apply ready
0Pilot phases
Role-owned phases before exact apply, send, upload or release gates.
601-610
Pilot Workflow Charter
One reviewed journey, record scope, gate map and QA model before workflow build.
Core: pilot scope, role gate matrix, QA evidence model
Surfaces: Settings, Dashboard, Sync
Gate: No production or public release approval.
611-620
Owner Property Check Flow
Owner or internal property check is traceable in CRAYS Core Dev/Pilot scope.
Core: property case, owner profile, property fit gates
Surfaces: CRM, Real Estate, Files, Analytics
Gate: Owner submission writes and uploads remain closed without exact approval.
621-630
Location, Rent and Deal Economics
Property, evidence, rent potential and deal economics are reviewed from Core records.
Core: location evidence, rent potential, deal economics, benchmark KPI
Surfaces: Analytics, ERP, CRM, Files
Gate: Live external reads and finance writes remain closed.
631-640
Prepared Deal Assembly
Internal package joins property, evidence, economics, files, project and CRM signals.
Core: prepared offer, evidence package, document package, project signal
Surfaces: CRM, Files, Project, ERP, Analytics
Gate: Candidate and public release remain closed.
641-650
Candidate Deal Room Pilot
Candidate sees only release-gated package, evidence, economics, questions and status.
Core: candidate deal room, released evidence shell, candidate question thread
Surfaces: Candidate Portal, CRM, Files, Chat
Gate: Regulated checks and external sending remain closed.
651-660
Candidate Evidence and Intent
Candidate questions, intent and checklist actions become controlled Core command intent.
Core: candidate intent, candidate checklist, communication event, core command
Surfaces: Candidate Portal, CRM, Files, Loans
Gate: Bank workflow start remains closed without exact approval.
661-670
Bank Evidence / Financing Package
Bank Partner receives a release-gated pilot shell with evidence and checklist status.
Core: bank package shell, evidence classification, loan checklist, condition status
Surfaces: Loans, Files, ERP, Bank Partner Portal
Gate: Bank send, payment and lender release remain closed.
671-680
Franchise Partner Opening Handoff
Approved internal candidate state feeds opening tasks, milestones, files and contacts.
Core: opening project, milestone, document checklist, contact map
Surfaces: Project, Files, Operations, ERP, Support
Gate: Tool/source apply remains closed without exact approval.
681-690
Cross-role Dashboards and Audit
Every role sees one scoped Core truth through dashboards, events, KPIs and blockers.
Core: workflow event, KPI snapshot, audit event, gate state
Surfaces: Dashboard, Analytics, CRM, Project, Loans
Gate: Unreviewed visibility expansion remains closed.
691-700
Pilot Closeout / Release Decision
Full pilot evidence, QA, audit and gate review decide what can move toward beta.
Core: pilot evidence report, QA result, gate review, release decision
Surfaces: Settings, Analytics, Dashboard, Files
Gate: No automatic production approval.
Property intake
Property fit and handoff
Review property fit, evidence, documents and handoff readiness before the deal moves into the next workflow.
Property cases
0Handoff ready
0Location
0/0Documents
0/0Events
0Apply ready
0Current property case
Use this workspace to qualify the property and prepare the next handoff.
Location, Rent and Deal Economics pilot
Location and rent economics
Location evidence, rent potential, benchmark KPIs and deal economics are reviewed from shared CRAYS Core records before package assembly.
Pilot cases
0Prepared offers
0Location
0/0Current rent
0Current economics
0Benchmark ready
0/0Current economics review
The pilot case stays internal until rent, economics and finance review are ready.
Prepared Deal Assembly pilot
Prepared deal assembly
Property, evidence, documents, economics, Project signals and CRM activity are assembled into an internal package view before any Candidate or Bank release.
Packages
0Prepared offers
0Evidence
0Documents
0/0Project signals
0CRM signals
0Internal package assembly
The package is internal until the next release-gated Candidate flow approves sections.
Candidate Deal Room pilot
Candidate deal room
Candidate-facing package sections, questions and intent preparation stay release-gated while Deal Manager reviews the shell from real CRAYS Core pilot state.
Internal packages
0Candidate-visible
0Sections
0Release required
0Ready gates
0/0Messages
0Candidate room stages
Sections and questions are visible only as a controlled shell until release approval.
Candidate Evidence and Intent pilot
Candidate evidence and intent
Candidate questions, intent and review checklist actions are modeled as guarded CRAYS command boundaries while release, regulated and bank workflows stay closed.
Internal packages
0Candidate-visible
0Evidence
0Intent records
0Action models
0Ready gates
0/0Candidate action stages
Candidate actions are command-modeled here, not executed.
Guarded action models
Each action names the operating boundary and the review state that remains closed.
Bank Evidence and Financing Package pilot
Bank evidence and financing
Finance package prerequisites, document evidence, Candidate intent signals and Bank Partner shell state are reviewed in CRAYS while all lender release, sends, uploads and finance writes stay closed.
Bank packages
0Loan cases
0Candidate intents
0Documents
0Work items
0Ready gates
0/0Financing stages
Each stage has an owner, a gate and an explicit current state.
Financing work queue
Work items name owner, CRAYS boundary, next action and closed release gate.
Opening Handoff pilot
Opening handoff
Approved internal readiness feeds a Project and Operations handoff cockpit with partner milestones, work items, pages and stakeholder scopes while tool apply and external notifications stay closed.
Project items
0Handoff items
0High priority
0Blocked
0Actions
0Ready gates
0/0Handoff milestones
Milestones show owner, readiness and the next operational action.
Handoff action queue
Actions are command-modeled and gated before any apply or external notification.
Cross-role pilot audit
Cross-role audit
One scoped control tower for the end-to-end pilot chain: property, evidence, economics, Candidate intent, bank readiness and opening handoff.
Segments
0Ready
0Blocked
0Release required
0Locked
0Audit events
0North Star chain
Each row is a value-stream segment, not a standalone dashboard tile.
Audit events
Pilot closeout and release decision
Pilot closeout and release decision
The pilot is reviewed as one operating chain. Beta scope can be prepared, but production, releases, external reads, writes, sends, uploads, bank actions and payments stay closed.
Pilot blocks
0Segments
0Decisions
0Beta-ready
0High risks
0Gates
0Release decisions
Each decision separates beta preparation from release execution.
QA evidence
Gate decision register
Controlled beta readiness
Controlled beta release
Beta work is prepared as explicit scope, room, gate and recovery decisions. Nothing launches, deploys, releases, writes, uploads, sends or pays until a later exact gate opens it.
Beta blocks
0Prepared
0Blocked
0Gate prep
0Rooms
0Side effects
0Beta block register
Each block defines the work outcome and the gate that remains closed.
Exact gate preparations
Operations and support queues
Operating control room
Platform work control
Coordinate role queues, active cases, handoffs, stakeholder rooms and closed execution gates from one working surface.
Workstreams
0Ready controls
0Prepared controls
0Role queues
0Case workspaces
0Open gates
0Work queues
Every role starts from owned work, records and next action.
No queue selected.
Case workspaces
Workflow actions
Cross-module handoffs
Prepared deal factory
Prepared deal decision chain
Property owner fit, property supply, location evidence, deal economics, Candidate intent, bank package readiness and opening handoff as one CRAYS data chain.
Coverage
...Stages
...Boundaries
...Writes
0Next review
Product decisionFactory chain
Every prepared deal must trace through these governed stages.
Required decision data
Provider evidence architecture
Evidence architecture
Internal evidence lanes for Location Intelligence, Property Feed, Banking Evidence and Source Work Items before any live read, write, upload or release.
Blocks
...Evidence lanes
...Adapter guards
...Live calls
0First path
Location IntelligenceEvidence lanes
Each lane converts external or source signals into CRAYS-owned evidence before release.
Adapter guards
Location Intelligence decision
Location Intelligence decision
Read-only adapter decision for reachability, travel-time, statistics, places and score evidence. The next step is a no-call scaffold, not a live provider read.
Decision
Read-onlyRead classes
...Field policies
...Live read
OffNext block
...Allowed read classes
Each class defines bounded inputs and CRAYS-owned derived evidence.
Field policies
Provider Evidence program
Evidence program
Controlled CRAYS evidence layer for location, property, rent, deal economics and banking readiness. Default mode is no-call and no-release.
Blocks
...Mode
No-callEvidence surfaces
...Core tables
...Live reads
OffBlock groups
Prepared program layers before any sandbox or live provider decision.
Sandbox pilot
Sandbox decision pilot
Controlled sandbox and pilot readiness for location, property, banking, owner submission, economics and release shells. Execution remains off by default.
Coverage
...Mode
Sandbox-readySandbox paths
...Pilot surfaces
...Execution
OffDecision layers
Sandbox and pilot readiness layers before any selected execution gate.
Adapter health
Module readiness
Project, CRM, ERP, Files and Sync readiness in one read-only view.
Schema ready
...Accessible
...Internal counts
...Blocked scopes
...Write actions
...Modules
Core domain
Data readiness
Schema status, domain surfaces and guarded write boundaries for prepared offers, properties, bank packages, documents and sync.
Schema
CheckingSurfaces
...Records
...Missing tables
...Domain surfaces
Permission matrix
Initial CRAYS-native permissions for this settings area.
Allowed roles
Scopes