Merphils

The core product decision was to treat identity as shared across schools, roles, and relationships rather than forcing separate accounts for every context.

That framing made it possible to design around one learner history, one family surface, and one person moving between roles like owner, staff member, parent, or student.

The platform is being shaped around strict access boundaries so each school only exposes the information relevant to that context while still preserving continuity for the user.

The experience has to make context-switching feel simple for families and administrators without weakening privacy or permission controls behind the scenes.

The platform is being structured around the daily jobs schools and families need to complete, from classes and assignments to admissions, grades, and finance.

That keeps the product grounded in operational clarity instead of letting the access model become an abstract architecture exercise.

Current product work is focused on the workflows schools need immediately, including classes, assignments, grades, academic history, admissions, and finance.

At the same time, the structure is being kept flexible enough to support future network features like tutor discovery, study circles, and resource sharing across education contexts.

Right now the work is centered on tightening the relationship between identity, permissions, and the operational surfaces schools and families will use most often.

The immediate goal is to get the core school workflows feeling stable and coherent before broader collaboration features become part of the next phase of the product.