About
Directory software usually starts from a schema. This one starts from your file.
Most organisations that need a directory already hold the data. It sits in an export from an old system, a spreadsheet turned into JSON, or an endpoint someone built years ago. The hard part is not storage. It is deciding what each field means and who is allowed to change it.
What we are building
Bobby Directory turns an export into a directory that can be moderated, delegated and published without giving away administrative control. The people who run a profile get a place to work that is not the administrator interface.
The product is built in approved phases. Each phase states its boundary, and no capability is switched on before the review that covers it.
The four surfaces
- Public website
- What visitors and published directories see.
- Profile Studio
- Where an invited profile collaborator works.
- Workspace Console
- Where a directory is run day to day.
- Platform Admin
- Where the platform itself is operated.
Principles
Show before you commit
No import, no publication and no invitation happens without an explicit confirmation that shows the consequence first.
Least privilege everywhere
Roles are narrow on purpose. Convenience never justifies handing someone more reach than their work needs.
Say what is off
A capability that is not built is stated as not built. There is no placeholder pretending to work.
Plain language over jargon
Technical keys become readable names, and states are described in words a profile owner understands.
Auditable by default
If an action changes something meaningful, it is recorded and attributable.