fow_goal
Model intended software behavior by recording use cases, sequences, and expectations, linking goal nodes, and deriving requirement candidates for a project graph.
Instructions
Describe intended software behavior as use cases, ordered sequences and behavioral expectations, then link and inspect those goal nodes or derive requirement candidates. Route with operation: view, add_use_case, add_sequence, add_behavioral_expectation, link, derive_requirement_candidates. Prerequisites: Use an existing project and canonical graph-node identities for links. Effects: view reads the graph; authoring appends use cases/sequences/expectations/links. Candidate derivation uses the recorded goal graph without inference; candidates do not silently become requirements. Exact help (replace operation_name with the selected route): fow_capabilities({"view":"operation","operation_tool":"fow_goal","operation_name":"view"}).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| view | No | Goal-graph projection selected by operation=view; use the canonical views listed in exact operation help. Applies to: view. Canonical values: summary, nodes, edges, candidates. | summary |
| actor | No | Identity of the human or agent recording this action; retain the original identity when replaying its request. | |
| limit | No | Maximum number of records in this read page; existing route-specific bounds still apply. Applies to: view. | |
| title | No | Short human-readable title of the authored requirement, finding, packet, run step or campaign. Applies to: add_use_case, add_sequence, add_behavioral_expectation. Required by: add_use_case, add_sequence, add_behavioral_expectation. | |
| offset | No | Zero-based position of the first record in this bounded read page. Applies to: view. | |
| category | No | Requirement or behavioral-expectation category recognized by the current lifecycle policy. Applies to: add_behavioral_expectation. Required by: add_behavioral_expectation. Canonical values: functional, non_functional. | |
| relation | No | Canonical directed relationship between the selected source and target goal nodes. Applies to: link. Required by: link. | |
| objective | No | Observable objective of the use case or implementation run. Applies to: add_use_case. Required by: add_use_case. | |
| operation | Yes | Operation selector for this multiplexer; use a canonical route listed below. Canonical values: view, add_use_case, add_sequence, add_behavioral_expectation, link, derive_requirement_candidates. | |
| statement | No | Precise requirement or behavioral expectation describing an observable obligation. Applies to: add_behavioral_expectation. Required by: add_behavioral_expectation. | |
| invariants | No | Conditions that must remain true throughout the scoped behavior or change. Applies to: add_use_case. | |
| project_id | Yes | Canonical lifecycle project ID. Select the existing project explicitly; development Markdown authorities are separate from runtime projects. | |
| request_id | No | Caller-owned retry identity. For receipted mutations replay the same actor and contents; changed contents can conflict. Inspect exact operation help for its receipt policy. | |
| detail_level | No | Read projection detail level; standard is bounded routine context, audit includes the available audit detail. Applies to: view. Canonical values: standard, audit. | standard |
| normal_steps | No | Ordered normal use-case/sequence actions describing the intended successful behavior. Applies to: add_sequence. Required by: add_sequence. | |
| participants | No | Named actors/components participating in the use case or sequence. Applies to: add_sequence. Required by: add_sequence. | |
| failure_steps | No | Ordered steps describing how the use case behaves when its normal operation fails. Applies to: add_sequence. | |
| preconditions | No | Conditions assumed before the use case starts. Applies to: add_use_case. | |
| source_anchor | No | Optional structured source anchor containing source_path, integer line_start and line_end, and optional label; this goal-authoring input is a mapping, distinct from requirement/finding string references. Applies to: add_use_case, add_sequence, add_behavioral_expectation. | |
| postconditions | No | Conditions that should hold after the use case completes. Applies to: add_use_case. | |
| source_goal_id | No | Existing source goal node for the directed goal relationship. Applies to: link. Required by: link. | |
| target_goal_id | No | Existing target goal node for the directed goal relationship. Applies to: link. Required by: link. | |
| use_case_actor | No | Stakeholder/system role performing the use case, distinct from the actor recording this mutation. Applies to: add_use_case. Required by: add_use_case. | |
| alternate_steps | No | Ordered alternative use-case steps, distinct from the normal and failure paths. Applies to: add_sequence. | |
| expected_effects | No | Observable effects expected from the authored use-case or sequence steps. Applies to: add_sequence. Required by: add_sequence. | |
| observable_outcome | No | Result the stakeholder should be able to observe when the use case succeeds. Applies to: add_use_case, add_behavioral_expectation. Required by: add_use_case, add_behavioral_expectation. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||