Turn business requirements into reusable, testable actions for people, apps, and agents.
The Use Case Tree Method organizes a business capability into smaller use cases with outcomes, participants, and dependencies. Reuse a capability wherever the same business work is needed.
In Legra, that description is workspace knowledge. Connect it to the actions that perform the work and the tests that describe a correct result.
A Story names an action for a persona, with defined inputs and outputs. Its implementation connects that action to a query, code, or an external service under the applicable execution contract.
For example, a mortgage use case includes actions to check income and produce a quote. A test describes the result expected for a particular set of inputs.
Develop use cases, Stories, and tests on branches. Review their changes alongside the knowledge they use. An app or agent invokes the authorized action rather than reconstructing its business meaning independently.
A parent Use Case can delegate smaller Use Cases to other workspaces through native Story calls. Each executes under its own authority near the knowledge it needs. A lender's quotation can request a collateral eligibility answer computed on the customer's Host, without retrieving the property records. Follow the mortgage example.
Business specifications by example explains scenario execution, results, and promotion checks.
Developer reference
Use Case resources link outcomes, personas, Stories, implementations and scenarios. A Story declares input/output concepts; implementations map those concepts to executable parameters and values.
A SPARQL implementation can bind applicant/date inputs and return verified-income output. The query text implements the requirement; it does not become the requirement's stable identity. External services can implement the same declared interface.
Resolve implementation in deployment/workspace context, then check principal authority and funding. Invocation emits attributable inputs, outcome and execution IDs. BDD scenarios assert typed results or state changes. Apps edit and invoke this shared model rather than maintaining an independent specification database.
Cross-workspace calls bind a destination Use Case/Story, execution workspace, input bindings and permitted output concepts. The receiving Host applies that workspace's authority. Results feed the parent operation; task-tree identity correlates execution while workspace transactions remain local.