Spec work, not commissioned. Built from the lines of a listing that asked for a reviewed blueprint, a community structure with access groups, the lifecycle workflows of four named programs, a CRM connection, a check for conflicting actions, tests and a handover. The structure and rules are a proposal to review against the client's own blueprint.
Live plan: https://demos.mc.mightyhouseinc.com/6337ylmn-membership-ops/
Structure: https://demos.mc.mightyhouseinc.com/6337ylmn-membership-ops/structure.html
Workflows and the conflict check: https://demos.mc.mightyhouseinc.com/6337ylmn-membership-ops/workflows.html
Integration: https://demos.mc.mightyhouseinc.com/6337ylmn-membership-ops/integration.html
Tests and scope: https://demos.mc.mightyhouseinc.com/6337ylmn-membership-ops/delivery.html
What it has, line by line from the listing
Space groups, their spaces, the access groups and a permission matrix of four rights.
One access group per named program; the build checks each program carries the full event set.
Twenty lifecycle rules as data: program, event, condition and the change to access.
An event map between the CRM and the platform, each row with direction, method and status.
A conflict and duplicate check, run on the rules (no findings) and on a seeded bad pair (both caught).
Eight access tests with the state the systems must end in, five of them critical, plus the handover list.
What the fixed price covers, what it does not, the risks and the other running costs.
The plan
Structure
Workflows and the conflict check
Tests and scope
0 likes · 1 view · Oct 27, 2026
Spec work, not commissioned: the space and access-group structure for a training community, every lifecycle rule written as data, a check that finds conflicting and duplicate rules, the CRM event map with the unsupported item named, access tests and a scope with costs.
