Seeded accounts
Demo identities and what each one is useful for
The seed script creates predictable demo accounts with the development password Roundtable2026!Demo. This password is for local demonstration only. Do not reuse it in a real environment, and do not paste it into production secrets.
Government accounts
| Role | Command | Good demo for | |
|---|---|---|---|
sysadmin@navy.mil | GOV_SYSTEM_ADMIN | NAVWAR | Enterprise visibility, command creation, editing, deletion, and reparenting. |
admin@navy.mil | GOV_ADMIN | NIWC PAC | Enterprise ledger visibility, publishing, user administration within admin policy, and exports. |
lead.navsea@navy.mil | GOV_COMMAND_LEAD | NAVSEA | Own-command workflows and a clear denial when attempting a child command. |
lead.niwcpac@navy.mil | GOV_COMMAND_LEAD | NIWC PAC | Command-scoped engagement and coordination examples. |
poc.ai@navy.mil | GOV_POC | NIWC PAC | AI/ML and autonomy matching notifications. |
poc.c4i@navy.mil | GOV_POC | PEO C4I | C4I, networks, communications, and tactical-edge tags. |
poc.cyber@navy.mil | GOV_POC | NIWC LANT | Cyber, zero-trust, and electronic-warfare matching. |
poc.unmanned@navy.mil | GOV_POC | PEO USC | Unmanned surface and undersea systems matching. |
poc.undersea@navy.mil | GOV_POC | NUWC NPT | Sonar, acoustics, and undersea warfare matching. |
The seed's exact names and titles are in the government user creation blocks in prisma/seed.ts. Interest profiles are created for the five POC accounts and point to seeded portfolio nodes.
Industry contacts
The seed creates one industry contact for each organization. The email is generated as contact@<slug>.example.com, where the organization name is lowercased, punctuation is replaced with hyphens, and leading/trailing hyphens are removed.
| Organization | Type | Location | Capability tags | Contact email pattern |
|---|---|---|---|---|
| Pelagic Dynamics | COMPANY | San Diego, CA | uuv,autonomy,acoustics | contact@pelagic-dynamics.example.com |
| Quartermast AI | COMPANY | Austin, TX | ai/ml,llm,predictive maintenance | contact@quartermast-ai.example.com |
| Ironclad Networks | COMPANY | Reston, VA | zero trust,networks,cybersecurity | contact@ironclad-networks.example.com |
| Littoral Robotics Group | COMPANY | Panama City, FL | usv,mine warfare,autonomy | contact@littoral-robotics-group.example.com |
| Applied Physics Laboratory, Johns Hopkins University | UARC | Laurel, MD | hypersonics,undersea,ai/ml,space | Generated from normalized slug |
| Monterey Bay Autonomy Lab | ACADEMIA | Monterey, CA | autonomy,uuv,machine learning | contact@monterey-bay-autonomy-lab.example.com |
| Sable Peak Energetics | COMPANY | Ridgecrest, CA | energetics,propulsion,hypersonics | contact@sable-peak-energetics.example.com |
| Halyard Cloud Systems | COMPANY | Arlington, VA | cloud,devsecops,software factory | contact@halyard-cloud-systems.example.com |
Demonstration recipes
contact@pelagic-dynamics.example.com and open the portal profile to see UUV, autonomy, and acoustics tags.uuv,autonomy. The matching engine should consider the Unmanned Maritime Systems and Undersea Warfare nodes.poc.unmanned@navy.mil or poc.undersea@navy.mil to inspect the resulting notification.admin@navy.mil to view the organization and route an engagement, then compare the enterprise view with lead.navsea@navy.mil.Resetting demo state
The seed is designed to be idempotent for core accounts and organizations. It does not mean every user-generated submission or notification is deleted on each run. Use a disposable development database when you need a clean demonstration.
What seed is idempotent about
The command and account creation code uses existing names, abbreviations, and emails to avoid duplicating core fixtures. Existing command hierarchy changes are preserved rather than blindly overwritten. Portfolio nodes and organizations are similarly looked up by their seeded names. This is useful for repeated setup, but a dirty database can contain additional records that are not in the demo tables above.
A role-comparison exercise
- Use
lead.navsea@navy.milto inspect NAVSEA-owned work. - Try to edit a child such as NSWC Dahlgren; the exact-command rule should deny it.
- Use
admin@navy.milto confirm enterprise visibility but attempt hierarchy reparenting; the system-admin-only gate should deny it. - Use
sysadmin@navy.milto perform a controlled reparent in a disposable database.
This exercise demonstrates the distinction between “can see enterprise records” and “can reorganize authorization structure.”