Find the right item
Browse the document hierarchy or filter loaded work items. Use workspace search for a wider view.
Define the system. Give AI real context.
From engineering intent to connected specifications.
Define your system, structure engineering knowledge, and connect requirements. Give engineers and AI agents the context they need to build.
No account required.
One engineering workspace.Real application · fictional thermal-controller project
01 / Work in context
Keep the system within reach.
Requirements rarely make sense on their own. Keep project navigation, the specification and the selected item together, so the next engineering question doesn’t start in another document.
Keep the reasoning
Write a requirement alongside its rationale and configurable attributes. Discuss it in item-level comments.
Follow its relationships
Inspect linked engineering objects, then open the context behind the requirement.
02 / Define the system
Start with the problem. Make the intent explicit.
Capture why the system is needed, how it will operate and what it must be able to do. Develop functions from capabilities while keeping the original engineering intent available for review.
- Problem statement
- Mission objectives
- Concept of operations
- System capabilities
- Functional decomposition
04 / Connect the engineering
See the links. Find what’s missing.
Understand which requirements have relationships to system capabilities—and which need attention. Inspect explicit links in a cross-specification matrix, then follow the connected objects during engineering review.
Inspect relationships
Use saved cross-specification matrices to navigate connected engineering information.
Review gaps
Filter orphan objects and inspect stale links when relationship endpoints are missing.
Maintain explicit links
Create and review relationships between requirements, capabilities and other engineering objects.
05 / AI with engineering context
Ask for a review. Keep the engineering judgment.
Request requirement feedback or a targeted wording improvement from the selected item. AI assistance uses the context supplied by the workflow; proposed field updates need your evaluation and acceptance.
- Select the engineering object
- Request review or improvement
- Evaluate proposed changes
- Accept deliberately
Derivation tools can also propose requirements from capabilities. Organization AI profiles and published prompt template sets configure supported assistance. AI output does not establish correctness or certification.
07 / Preserve and exchange
Keep a reference. Review incoming change.
Capture the project as a named snapshot for later restoration or export. Exchange engineering content through ReqIF, and inspect before/after differences when reviewing an incoming ReqIF import.
Inspect an actual ReqIF import comparison
- ReqIF / ReqIFZ exchange
- Markdown specifications
- CSV / text traceability exports
- Markdown / text definition summary
Also in the workspace
Support the work around the requirement.
Safety engineering objects
Maintain hazards, safety goals and safety-related requirements with explicit relationships.
Read-only Viewer
Read and navigate engineering information without entering the editing workflow.
Project files
Organize supporting files alongside the project’s engineering information.
Item-level discussion
Keep comment threads attached to the engineering object being discussed.
Configurable engineering data
Adapt types, attributes and enumerations to the project’s needs.
AI configuration
Manage organization AI profiles and choose published prompt template sets.
Follow the guided remote-unlock example
One request. Follow the decisions.
Illustrative public demo · sample answers and proposals · no sign-in required
Illustrative decision status
3 unresolved · 0 deferred · 3 proposed requirements depend on these decisions.
Unresolved: offline behavior, confirmation timeout, access revocation.
This teaching view is not a product completeness score. Further engineering questions can remain after every sample answer is selected.
Capture request
Feature request
“Let users unlock the door from the app.”
Operating context
A resident uses a mobile app, an access service and a connected door controller. Connectivity can fail between a request and physical actuation.
SCN-01 · Remote unlock
Trigger: the resident selects Unlock. An authorized resident gains access when the controller reports the lock physically unlocked. Request acceptance alone is not confirmation.
In scope: the app, access service, command dispatch and physical confirmation. Mechanical key access and emergency egress design are outside this example.
Choices stay in this page’s memory. Resetting or reloading restores the sample; nothing is saved to a real project.
Define. Connect. Share.
Give your next engineering decision a connected starting point.
See how system intent, requirements and relationships fit together. Then try the workspace with a fictional system.
No account required. Compare plans.