Every module reads as a numbered specification and edits as a grid. Rich text, tables, diagrams and custom attributes live on the same object, and the whole team can work in it at once.
The continuous document view renders a module with hierarchical section numbers, formatted bodies, embedded tables and images, and attribute chips under each object. Insert a sibling or a sub-requirement exactly where it belongs, then print the module or save it as a PDF.
Requirement bodies are rich text: headings, lists, tables and images, edited in a toolbar editor next to the attribute form. Content is sanitised on the server before it is stored.
Attributes are typed as string, number, date, boolean or enum, so values such as a DAL or a verification method are picked from a defined list.
The grid lists a module with the columns your saved view selects. Unlock in-place editing to change status, priority or any attribute right in the cell; Enter saves and Escape cancels. A compact density fits more rows on screen.
There are no module locks. Each save carries the version it was based on, so if someone else changed the object first you get a clear conflict instead of a silently lost update.
Each module numbers its objects with its own prefix and padding, such as SRS-001 or SWR-031. Numbers are never reused.
Terms defined in the lexicon are underlined in read-only bodies, with the definition on hover. The stored text is untouched.
Each user picks System, Light or Dark; System follows the operating system setting.