Show only policies matching the selected status.
A mission.
From plan to review.
Explore the workflow with sample data. Everything here runs in your browser tab. No real agents, tests, repositories, or pull requests are connected.
Sample mission workspace
Explore a mission: choose BM-139, simulate a failure, rerun, inspect the evidence, and record a human decision.
No missions in this view. Choose another filter or reset the demo.
Add policy status filter
Filter the policy list by status and preserve the selection when navigating back.
- Responsibility
- Implementer · Agent 01
- Requirements
- 2 defined
- Human confirmations
- 0 / 2
The sample is ready for human review. These results do not verify a real implementation.
Use “Simulate validation” to explore execution and evidence.
Inspect Verify for the failure, then simulate a rerun.
- Review the acceptance criteria and project conventions.
- Implement the filter in an isolated workspace.
- Collect verification evidence and request human review.
- Dependencies
- Independent sample mission
- Execution limit
- Configured per mission in the private product
- Workspace
mission/BM-142· illustrative
Required field message
Expected: “Enter a policy name.”
Received: “This field is required.”
Preserve the selection after navigating away and back.
No real tests executed. Confirmations here are sample human decisions, not independent verification of code.
- show all policies+ read the remembered status selection+ show policies matching that status+ persist the selection when it changes+ scenario: select an active status+ expect: only matching policies are visible+ scenario: navigate away and return+ expect: the previous selection is preserved- Review
- Awaiting a human decision
- Changed files
- 2 illustrative files
- Commits / pull request
- Not connected
The report distinguishes simulation results, sample confirmations, and approval. No pull request is created or merged.
Mission activity
- Mission requirements captured
- Implementation responsibility assigned
- Simulated changes and verification evidence collected
This changes the preview only. No code is verified, published, or merged.
Knowledge that follows the mission.
The private product stores project knowledge with its source and update history. This sample is read-only.
Source: sample owner architecture decision
OWNER PROVIDEDYour workflow. Defined once.
- Prepare
- Set up the execution environment
- Build
- Validate the project build
- Verify
- Run the project's test recipes
- Clean up
- Release temporary resources
Recipe configuration is supported in the private product. Real recipe execution is not connected yet.
Demo only. Your actions stay in this browser tab.
Add policy status filter
Filter the policy list by status and preserve the selection when navigating back.
- Responsibility
- Implementer · Agent 01
- Requirements
- 2 defined
- Human confirmations
- 0 / 2
The sample is ready for human review. These results do not verify a real implementation.
Use “Simulate validation” to explore execution and evidence.
Inspect Verify for the failure, then simulate a rerun.
- Review the acceptance criteria and project conventions.
- Implement the filter in an isolated workspace.
- Collect verification evidence and request human review.
- Dependencies
- Independent sample mission
- Execution limit
- Configured per mission in the private product
- Workspace
mission/BM-142· illustrative
Required field message
Expected: “Enter a policy name.”
Received: “This field is required.”
Show only policies matching the selected status.
Preserve the selection after navigating away and back.
No real tests executed. Confirmations here are sample human decisions, not independent verification of code.
- show all policies+ read the remembered status selection+ show policies matching that status+ persist the selection when it changes+ scenario: select an active status+ expect: only matching policies are visible+ scenario: navigate away and return+ expect: the previous selection is preserved- Review
- Awaiting a human decision
- Changed files
- 2 illustrative files
- Commits / pull request
- Not connected
The report distinguishes simulation results, sample confirmations, and approval. No pull request is created or merged.
Mission activity
- Mission requirements captured
- Implementation responsibility assigned
- Simulated changes and verification evidence collected
This changes the preview only. No code is verified, published, or merged.
Improve validation messages
Show useful field errors and move keyboard focus to the first invalid input.
- Responsibility
- Tester · Agent 02
- Requirements
- 2 defined
- Human confirmations
- 0 / 2
The sample is ready for human review. These results do not verify a real implementation.
Use “Simulate validation” to explore execution and evidence.
Inspect Verify for the failure, then simulate a rerun.
- Review the form's field labels and error states.
- Update validation copy and keyboard focus behavior.
- Check the evidence before requesting approval.
- Dependencies
- Independent sample mission
- Execution limit
- Configured per mission in the private product
- Workspace
mission/BM-139· illustrative
Required field message
Expected: “Enter a policy name.”
Received: “This field is required.”
Show a specific message for a missing policy name.
Move keyboard focus to the first invalid field.
No real tests executed. Confirmations here are sample human decisions, not independent verification of code.
- show a generic validation summary+ show an error beside the affected field+ describe how to correct the value+ focus the first invalid field on submission+ scenario: submit without a policy name+ expect: Enter a policy name.+ expect: the policy-name field receives focus- Review
- Awaiting a human decision
- Changed files
- 2 illustrative files
- Commits / pull request
- Not connected
The report distinguishes simulation results, sample confirmations, and approval. No pull request is created or merged.
Mission activity
- Mission created from a manual requirement
- Field messages updated in the sample change set
- Simulation queued; first validation illustrates a failure
This changes the preview only. No code is verified, published, or merged.
Fix renewal date formatting
Display renewal dates consistently, including missing values and local date boundaries.
- Responsibility
- Reviewer · Agent 03
- Requirements
- 2 defined
- Human confirmations
- 0 / 2
The sample is ready for human review. These results do not verify a real implementation.
Use “Simulate validation” to explore execution and evidence.
Inspect Verify for the failure, then simulate a rerun.
- Review the project's date display convention.
- Apply consistent formatting and empty-state handling.
- Collect regression evidence for owner review.
- Dependencies
- Independent sample mission
- Execution limit
- Configured per mission in the private product
- Workspace
mission/BM-137· illustrative
Required field message
Expected: “Enter a policy name.”
Received: “This field is required.”
Format renewal dates consistently across the interface.
Handle missing values without changing the calendar day.
No real tests executed. Confirmations here are sample human decisions, not independent verification of code.
- format with an implicit time-zone conversion+ preserve the calendar date+ apply the project's display convention+ show an empty state when the value is missing+ scenario: display a date near a time-zone boundary+ expect: the calendar day is unchanged+ scenario: display a missing renewal date+ expect: a useful empty state- Review
- Awaiting a human decision
- Changed files
- 2 illustrative files
- Commits / pull request
- Not connected
The report distinguishes simulation results, sample confirmations, and approval. No pull request is created or merged.
Mission activity
- Date boundary requirement recorded
- Sample change set and regression scenarios prepared
- Simulated verification passed; human review is next
This changes the preview only. No code is verified, published, or merged.