hub-pro-form-official

Implements the founder decision form UI and API with a stable 5-option schema and disk-first submit path.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill hub-pro-form-official-noetfield-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hub-pro-form-official
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/hub-pro-form-official
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill hub-pro-form-official-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It standardizes how agents and the founder interact with the Hub Pro decision form, enforcing a locked 5-slot question schema (choices A-D plus a free-text option 5) and a safe disk-first submit flow that avoids blocking the HTTP response. ## Core Features & Use Cases - Stable 5-slot schema: Every question row exposes 4 machine/agent choices plus an always-visible founder free-text slot, normalized via a single SSOT JSON schema. - Disk-first submit path: Applies picks synchronously in about 30ms, then runs reconcile, wire, judge, and governance steps in a background subprocess started after the HTTP response. - Founder-only guards: Requires founder_submit, hub_browser channel, and partial_batch support, with an agent-submit-forbidden flag to prevent misuse. - Use Case: An agent adds 2-4 answer choices to an open question; the machine appends slot 5, the founder picks options in the browser UI, and the submission is receipted to ~/.sina/hub-form-submit-receipt-v1.json. ## Quick Start Ask the agent to add two to four answer choices to an open question on the Hub Pro form, then verify the API returns five option slots per row.

Frequently Asked Questions about hub-pro-form-official

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit answers to the Hub Pro founder decision form?

POST to /api/live-founder-decision-form-v1 with action submit, founder_submit set to true, a picks object mapping question IDs to option letters, and partial_batch true when not all rows are answered. A receipt is written to ~/.sina/hub-form-submit-receipt-v1.json.

How many answer options does each form question have?

Every question has exactly 5 option slots: choices A through D plus slot 5, an always-visible founder free-text textarea. Agents may only add 2 to 4 choices; the machine always appends slot 5.

Why must the background submit processing start after the HTTP response?

The macOS threaded server drops the connection if a background subprocess is started before the response completes. The sync step applies picks to disk in about 30ms, then reconcile, wire, judge, and governance run in the background.

Can an agent submit the founder form directly from the CLI?

No. Submission is restricted to the hub_browser channel with actor founder, asf, or human, and the form-agent-submit-forbidden-v1 flag blocks agent submissions. Agents only contribute answer choices, never final picks.

How do I verify the form API returns the correct schema?

Run the curl e2e check against /api/live-founder-decision-form-v1 and count option_slots on the first open question; it must equal 5. The SSOT schema lives in data/form-official-question-schema-v1.json.