Small team, high accountability, direct ownership.
TavSin should not look like a faceless experiment. The project is operated by a tight group of builders who care about protocol engineering, product clarity, and deployment discipline.
Who should be listed here
The public site should identify the builder, the operator, and the security owner once the final launch roles are confirmed. Until then, the page documents the role structure rather than inventing names.
The operating model
Protocol engineering handles the smart-wallet logic, product design handles the operator experience, and launch operations handle key rotation, release discipline, and incident response.
- Protocol engineering: policy checks, account modeling, read layer, and SDK maintenance.
- Product and UX: landing page, dashboard flows, and launch narrative.
- Operations: deployment control, freeze authority, and incident handling.
How collaboration should work
A protocol this visible needs readable code, clear docs, and direct ownership. Public pages should make it obvious where issues go, how the release cycle works, and which parts are audited before wider rollout.
Why this page matters
A serious protocol does not hide its operators. It makes the people and roles behind control visible enough that users can understand who is responsible for risk.