BRIDGEPOD
HaoSecurity & IP Packet
Architecture and process summary. Describes the operating model only — no certification or compliance claims are made.
hao50427126@gmail.com
Seattle, WA
1 · The model I run today
- US production, China in test & staging. Production servers and user data stay in the US. The China team works only in test and staging environments, using masked real data. This is the model I run today in my current role — not a ready-made promise for a new engagement.
- IP assignment, in writing. Every engineer signs an IP assignment through their employment contract, so code ownership is documented and carried by the employment structure.
- Access as an operating standard. MFA and least-privilege access as the operating standard, with access revoked on or before the last day.
2 · Architecture
3 · Agreed before onboarding
For a new engagement, these are agreed before engineers receive access. Your technical leadership approves the standards; implementation responsibilities are documented for the agreed arrangement.
- Approved repositories and tools
- Account ownership
- Access levels
- Handling of production data
- Offboarding responsibilities
4 · Who owns what
| Responsibility | Owner |
|---|---|
| Product roadmap, architecture, engineering standards | Your technical leadership |
| Final technical interview and hiring decision | You or your designated technical lead |
| Code review and technical acceptance | Your designated technical lead |
| Recruiting coordination, screening, and evaluation logistics | Hao, within the agreed scope |
| Cross-border communication, operating issues, and risk follow-up | Hao — coordinates and provides visibility within the agreed scope |
| Employment, payroll, labor, and tax obligations | Allocated by the actual legal contract structure (see the note on employment) |