| Firm |
Your consulting company. Everything in NorthFloe belongs to one firm |
| Client |
A company your firm delivers for |
| Project |
Work for one client, with its own team, docs and features |
| Project docs |
The shared background for a project: five Business docs and three Technical docs |
| Feature |
One piece of work delivered on its own, keyed REQ-n per project |
| Requirement |
What a feature must do: a description, user stories and acceptance criteria |
| User story (S1…) |
Who needs something and why |
| Acceptance criterion (AC1…) |
One testable check that proves a story works |
| Spec |
How a feature will be built. Firm only |
| Task (T1…) |
A unit of build work linked to acceptance criteria, delivered as one pull request |
| Test case |
Steps that check one acceptance criterion |
| Run |
One execution of a test case, with screenshots and an outcome |
| Validated |
Every acceptance criterion has passed its tests |
| Change request |
A new feature that changes a delivered one |
| Module |
A product area used to tag and filter features |
| Portal |
Your firm’s own NorthFloe address and branding |
| MCP / access token |
How an AI coding assistant connects to NorthFloe on your behalf |