WeProject.ai · Systems engineering
Systems engineering in WeProject.ai
Capabilities
Author requirements
Requirements can be created, edited and organised against a project.
Requirements traceability
A requirement can be followed to the tasks that implement it and the verification that closes it.
Objective-to-task breakdown
Work decomposes objectives to constraints to requirements to tasks, each level navigable.
Verification records
A requirement can carry verification evidence and a pass or fail outcome.
Impact analysis
Changing an entity can be traced to everything downstream of it.
Equation engine
Derived values are computed from declared equations rather than typed in.
Trade-space comparison
Options are scored against weighted criteria and ranked.
Evidence
- Declared in apps/data-domain/seed-data/product-capabilities.json
- Resolved by apps/data-domain/scripts/check-alignment-registry.mjs
- Implemented in apps/frontend/src/views/EnhancedRequirements.tsx
- Implemented in apps/frontend/src/views/Baselines.tsx
- Implemented in apps/frontend/src/views/Decompositions.tsx
- Implemented in apps/frontend/src/views/Budgets.tsx
- Implemented in apps/frontend/src/views/AuditLog.tsx
- Implemented in apps/backend/services/ExportService.js
Security
Running with no outbound connection
The model provider is a configuration choice · Reference data ships with the deployment, not copied into each app · The data stores are yours
Identity and access
One session, verified by every product · Multi-factor authentication · Revocation is checked when a session is used, not only when it is issued · Redirects are allowlisted · Permission resolves on role AND calling application
How the software is kept honest
Dependency vulnerabilities fail the build · A measured quality position, published with its coverage · The marketing claims on this site are gated