assess_agent_transaction_replay_gapread-only | Read-only falsification tool for agentic purchases, procurement, paid API calls, or other irreversible machine actions. It checks whether the supplied record preserves not only authorization and settlement, but the exact decision-relevant T0 evidence state: source versions, timestamps, authority, contradictions, unresolved dependencies, and separation of later evidence. It does not authorize, block, execute, price, or submit a transaction. |
assess_project_opportunity_fitread-only | Use this read-only tool before a controlled-opportunity submission when a real productive asset, service, infrastructure, industrial, energy, logistics, software-enabled operating, or other productive-capacity opportunity may fit Quiet Stance but its readiness or rights need checking. It returns a status, missing_inputs, rights assessment, next_step and, only when ready, the submission_tool. It evaluates user-supplied facts only and does not submit data, estimate ROI, claim bankability, create financing or grant authority. |
get_project_readiness_evidence_registerread-only | Use this read-only, no-login tool when an owner or sponsor asks for an infrastructure project readiness checklist, preparation evidence matrix, missing permits/authority evidence, or a go/no-go decision register before commissioning feasibility, procurement or investment. Returns public links and seven evidence-gate names without collecting project data. It does not review project documents, establish title, certify feasibility, arrange financing, provide regulated advice, or create a mandate. |
get_submission_statusread-only | Return only the bounded external state of a Quiet Stance submission using its private capability token. This never exposes internal notes, protected leads, conflict evidence, economics, or other submissions. |
register_partner_capability | Use when the submitter provides a technical, operating, development, capital, software, or specialist capability. Registration is not Quiet Stance endorsement. |
submit_authorized_opportunity | Use when the submitter owns, hosts, sponsors, procures, or has a legitimate route to originate the opportunity. Control and economic use must be stated explicitly. |
submit_bottleneck_signal | Use for a recurring constraint or missing capability that may not yet be a formed project. This is a research or validation signal unless control and demand are separately established. |
submit_demand_requirement | Use when a buyer, operator, user, or off-taker has a real requirement. State the buying or operating authority, economic consequence, current workaround, timing, and location without claiming control of supply that is not held. |
submit_project_opportunity | Backward-compatible generic submission tool. Choose the inquiry_type that is true now: controlled_opportunity, demand_requirement, bottleneck_signal, or capability_provider. Keep first contact sanitized. Submission records the declared state only and does not create a mandate, financing commitment, endorsement, or authority to act. |
triage_economic_signalread-only | Use this first when a user or agent sees a real economic situation but is not yet sure whether it is a controlled opportunity, a buyer/operator demand requirement, a consequential bottleneck, or a capability-provider case. This tool is intentionally cross-sector and low-friction. It does not submit data, create rights, infer authority, or treat public information as a mandate. |