ShiftLead
Store manager operating system. Shifts, staff, and the daily brief.
shiftlead.tabronmerryhill.com
Cert valid. Expires 2027-02-13.
Open ShiftLead8 apps on this box · 8 reachable · certs 8 of 8 valid · no open problems
Read is the voice of this server. Read connects to all your apps. You say what you need, and Read works through them for you. This is the main door.
Prefer to go direct? Your app store holds every app on this server. Pick one and use it yourself, the regular way.
Open the app storeStore manager operating system. Shifts, staff, and the daily brief.
shiftlead.tabronmerryhill.com
Cert valid. Expires 2027-02-13.
Open ShiftLeadFamily dinner companion. Meals, budgets, and the table at night.
table.tabronmerryhill.com
Cert valid. Expires 2027-02-13.
Open TableIntake and the creation gate. Ask for something new the governed way.
enablement.tabronmerryhill.com
Cert valid. Expires 2027-02-14.
Open EnablementThe server looking at itself. Owner sign-in required.
house.tabronmerryhill.com
Cert valid. Expires 2027-02-13.
Open HouseDigital health clinic. Coaching, plans, and your record.
victorylap.tabronmerryhill.com
Cert valid. Expires 2027-02-12.
Open VictoryLapThe workflow layer. Processes turned into working systems.
readable.tabronmerryhill.com
Cert valid. Expires 2027-02-12.
Open ReadableLocal shops and orders. Deals from businesses near you.
daymarket.tabronmerryhill.com
Cert valid. Expires 2027-02-12.
Open DayMarketThe publication. Stories and the Gate, published from this house.
tabronmerryhill.com
Cert valid. Expires 2027-02-12.
Open The WorkflowWhat Read can do for you depends on your permission level. Simple, reversible help (L1) can happen right away. Work inside your business (L2) needs the right person signed in. Anything binding or hard to undo (L3 and L4) stops and waits for the authorized person to approve it. Someone who is not the owner does not get owner level actions.
Everyone gets Read and the orb on every page. What changes is access. The owner can ask Read across every app and all the data, because the owner has permission to all of it. A worker sees only the apps and data their permission covers, by their department and their leadership clearance. Same experience, different access.
A gate agent sits between you and the data. Every Read interaction passes through it and through your permission. Read has no special powers. If someone tries through Read to reach data they do not have permission for, the gate blocks it and logs it: who tried, when it was attempted, and what they tried to reach. That becomes an L4 escalation, and the alert goes out whether the attempt got through or was stopped. There is no level above L4.
Need access you do not have? You can request it inside the system. The alert goes to the person who approves that data, with a simple slider to grant the permission right then and there. One simple action, in the moment.
Sign-in comes to this door soon. Until then, this page is the shell: the store is real, and Read's panel shows where the conversation will live. The permission design above is baked in now; enforcement rides with the sign-in build.