Inkfire Platform
Decisions
Decision register
Open questions stay visible until they become a recorded decision, proposal or parked item.
Open
Are these the right department boundaries?
Review whether Management & Operations, Web, IT & Infrastructure, Service Desk, Marketing, and Finance & People reflect how Inkfire actually works.
Rationale / notes
Avoid baking an artificial org chart into dashboards and permissions before staff input.
Open
Which systems remain authoritative?
For every integration decide whether Inkfire only reads it, writes back to it, or will eventually replace it.
Rationale / notes
Source-of-truth ambiguity is one of the fastest ways to create duplicate or contradictory records.
Open
Exactly what should clients see?
Define which plan, ticket, billing, contract and site-care information is client-visible in Portal and SiteKit.
Rationale / notes
Portal exposure rules should be explicit before API fields are designed.
Open
Where is the MVP line?
Choose the minimum set of modules required to replace current operational pain without delaying release for advanced AI or remote support features.
Rationale / notes
Foundation, Clients, Work, Time and Plans should precede advanced WebOps and AI orchestration.