Authoritative first
Prefer the government agency, licensing board, tax authority, court, regulator, or official program that controls the requirement. Secondary summaries can help discovery but should not replace the controlling source for filing-ready facts.
Date every consequential fact
Forms, fees, processing methods, publication rules, tax registrations, renewal dates, and agency instructions should carry an effective or last-verified date whenever the information can change.
Separate law from workflow
A statutory requirement, agency instruction, common operational recommendation, and Mabnee workflow suggestion are different things. The interface should label the difference instead of blending them together.
Preserve the source record
For consequential items, Mabnee should retain the source title, issuing organization, source location, verification date, applicable state or locality, and the business facts that caused the requirement to appear.
Use confidence carefully
Missing information, conflicting agencies, local variation, professional-entity restrictions, ownership rules, tax elections, and unclear classifications should trigger a question or professional-review flag—not a confident guess.
Review before submission
The final application view should show the user what information will be submitted, where it will be sent, the current fee breakdown, the source used, and any unresolved assumptions.
Monitor changes
Activated state and industry modules should be rechecked on a defined schedule and when an agency announces a material change. A stale module should be labeled or taken out of filing-ready mode.
Record corrections
When an error is found, Mabnee should correct the active content, record what changed, identify affected workflows where practical, and avoid silently presenting the old requirement as current.