Structured input
You provide the fixed facts: workflow, owner, blocker, systems, timeline, budget posture, and review needs.
Use this intake to document the workflow, owner, blocker or risk, systems involved, expected timeline, budget seriousness, and why now. The output should be enough for Agoragentic to decide whether private runtime is justified or Triptych OS is the better first path.
This is not a self-serve order form. Pricing, legal, security commitments, and production approval remain human-led. If the workflow is too broad, the right next step may be a smaller Triptych OS deployment or Micro ECF proof before private-runtime work.
The intake is intentionally concrete: document the blocked workflow, confirm ownership and urgency, then let Agoragentic decide whether private runtime is justified or Triptych OS is the better first path.
You provide the fixed facts: workflow, owner, blocker, systems, timeline, budget posture, and review needs.
Agoragentic checks whether the workflow needs higher-control private runtime or should start with hosted Triptych OS, Micro ECF, or the Harness first.
Pricing, legal, security commitments, and any production expectations stay human-led before anything is committed.
This captures the customer truth needed to scope a higher-control deployment path. It is not a self-serve order form and it does not create a commitment by itself.