← Return to partner workspace

Production handoff

Automation seam

This prototype is the operational front end of an eventually supervised, standalone nonprofit-fundraising product. It owns its domain data, schemas, workflow state, permissions, governance, deployment, and automation lifecycle. It does not contain an AI backend and does not make autonomous funding decisions.

Reusable workflow stages

  1. Organization intake captures legal identity, mission, geography, budget, and contact context.
  2. Evidence and provenance separates sourced research from partner-entered facts and records evidence references without uploading files.
  3. Completeness validation identifies missing required facts and records the outcome.
  4. Funding-readiness analysis records hard gates, “No,” and “Not sure” states without inventing answers.
  5. Opportunity-matching inputs captures need, amount, timing, use, capital layer, current funding, and relationships.
  6. Recommended next action is derived transparently from missing profile and readiness conditions.
  7. Approval and handoff requires a human acknowledgment before export; export is explicitly not submission.

Portable state and system boundary

JSON export follows the provider-neutral workflow schema. It includes stage status, validation outcomes, timestamped state transitions, provenance, human approvals, partner data, and submission state. Osiris may build, manage, observe, evaluate, or orchestrate the product only through a versioned adapter contract. Project records and learned outcomes remain inside this product boundary. Only explicitly approved, provenance-linked, generalized lessons may cross that boundary; operating the product never mutates Osiris core state, governance, or canonical truth.

Human judgment gates

Legal status, evidence credibility, readiness exceptions, funder fit, material recommendations, external submissions, and lesson promotion remain human-reviewed. “Not sure” is preserved as an uncertainty, never converted into a fact.

Next production dependency

Before multi-organization use, add authenticated accounts, role-based permissions, encrypted durable storage, server-side schema validation, immutable audit events, consent and retention policies, safe document storage, and an approved submission connector. A separately deployed automation service may consume versioned workflow events through the adapter, but consequential actions must stop at an explicit approval gate.

Currently functional