Job & boundaries
A specific business responsibility, intended users, authorized scope, and explicit exclusions.
GHOST SYSTEM STANDARD
A governed structure for repeatable AI-assisted business work.
The standard converts one repeated business responsibility into a portable, reviewable operating package. It defines what the system may do, what it needs, when a person decides, how failure is handled, and how a release is evaluated and versioned.
EIGHT CONTROL CATEGORIES
The operating decisions that turn instructions into a system.
Context contract
Required, optional, unknown, not-applicable, and excluded inputs are separated before work starts.
Workflow & handoffs
Entry criteria, ordered stages, decision points, completion criteria, owners, and receiving systems.
Skills & tools
Reusable skills map to work stages; tools are labeled REFERENCE ONLY, CONFIGURABLE, TESTED, or LIVE.
Outputs & evidence
Named deliverables carry acceptance criteria, source requirements, and uncertainty disclosure.
Approval & failure
Approval packets, allowed decisions, timeouts, retries, reconciliation, escalation, and stop conditions are explicit.
Evaluation
Normal, missing-context, authority, failure, unsupported-claim, and output-quality cases test the package.
Version & release
Manifest, current version, change history, checksums, compatibility, limitations, and release state travel together.
REFERENCE ARCHITECTURE
Trigger → context → role work → decision → approval → output → log.
A workflow starts only on an authorized event. It checks required context, routes work through the defined role, pauses consequential action for the named human approver, produces the controlled output, and records the evidence and version used.
Authorized TriggerContext CheckRole WorkflowHuman ApprovalControlled OutputEvidence Log
Deployment state is evidence-based.
A blueprint may describe a technically explicit implementation without claiming that credentials, connections, or production tests exist. TESTED and LIVE labels require a separate implementation record.
Review Deployment Blueprints →PUBLIC STANDARD, PROTECTED PACKAGES
Review the method publicly. Access the implementation materials through ownership or membership.
Public pages explain the architecture, scope, release state, relationships, and package contents. Detailed prompts, templates, evaluation cases, deployment guides, and downloadable package files remain behind server-verified entitlements.