Mission integrity
Keep charitable, research, educational and humanitarian purposes distinguishable from commercial, private-membership and operational activity.
Board Structural Charter
Enterprise Structural Charter
A working master architecture for governance, mission stewardship, asset control, operating companies and the separate private-membership interface represented by SovereignAqua Imperium-Habour PMA.
A. Purpose
Formalize the architecture before execution.
The supplied charter establishes a Foundation-centered enterprise structure. This enhanced version separates the charitable governance chain from the PMA interface so that the PMA is not inadvertently presented as a subsidiary, owner or tax-exempt arm of the Foundation without executed legal documents establishing that relationship.
Asset separation
Identify who owns an asset, who uses it, what consideration applies and which agreement governs the relationship.
Financial discipline
Require authority, approval, documented valuation or allocation, accounting treatment and reconciliation before material transfers.
B. Structural Hierarchy
The Foundation enterprise architecture
The hierarchy below reflects the structure supplied in the charter while adding a clearly separated PMA interface layer.
Level 1 • Mission & Governance
SovereignAqua Foundation
501(c)(3) status: proposed/recognized status must be confirmed from governing and IRS records.
Board governance • charitable programmes • research • grants • public-benefit activities • mission stewardship
Level 2 • Management Layer
BWC Longhorn Management Group, LLC
Proposed management and coordination layer identified by the charter. Ownership, control and authority must be supported by executed formation and governance records.
Level 3 • Asset Holding Layer
Wyoming Asset Holding Company, LLC
Proposed asset-holding layer for assets that are actually titled, assigned, leased or otherwise placed under its authority.
Aquaculture & Food Systems
Production → Processing → Distribution → Retail / Food Service
Forestry & Environmental Operations
Forestry, conservation, environmental infrastructure and resource-management functions.
Security & Support Operations
Security, facilities, logistics and other operational-support functions where separately established.
Separate Private-Membership / Enterprise Interface
SovereignAqua Imperium-Habour PMA
Proposed private-membership enterprise/interface — not shown as a Foundation subsidiary unless executed documents establish that relationship.
The PMA can serve as a distinct contractual, membership, research, innovation, service or private-enterprise platform where its governing jurisdiction and documents permit. Its role should be defined by its own formation documents and by written agreements with any Foundation, management, asset-holding or operating entity.
With the Foundation
Possible interface: approved research collaboration, programme services, grant-funded work, licensing or other documented relationship consistent with the Foundation's governing purposes.
With Management / Operations
Possible interface: management services, technology, procurement, research support, membership services or other commercial/private arrangements supported by written contracts.
With Asset Holding
Possible interface: lease, license, asset-use agreement or other permitted arrangement. The PMA does not acquire title merely because it uses an asset.
Critical separation rule: the PMA is an interface, not an automatic ownership bridge. A transaction between the PMA and a Foundation-controlled entity must be separately authorized, documented, valued or allocated, recorded and reviewed for related-party, private-benefit, tax and jurisdictional consequences.
C. How the PMA Enters the Structure
It enters through defined legal relationships—not by assumption.
This is the cleanest way to incorporate the PMA into the enterprise architecture while preserving institutional separation.
1. Establishment
Create and maintain the PMA's own formation, membership, governance, jurisdiction and authority records before treating it as an operating entity.
2. Defined function
Specify whether the PMA is acting as a membership platform, research/innovation platform, service provider, contracting enterprise or another lawful function.
3. Contractual interface
Use written R&D, services, licensing, asset-use, procurement, funding or other agreements for each material relationship.
4. Separate accounting
Maintain separate books, accounts, invoices, receipts and transaction records appropriate to the PMA and each counterparty.
5. Approval gate
Require authorized approval and conflict review before related-party transactions or transfers involving Foundation-controlled entities.
6. Reconciliation
Match agreements to invoices, payments, deliverables, asset registers and accounting entries so every material transaction has an evidence trail.
D. Structural Intent
Six control objectives
01 — Mission
Preserve the Foundation's public-benefit purpose and board oversight.
02 — Separation
Keep charitable, commercial, asset-holding and private-membership functions distinguishable.
03 — Liability
Use separate entities, contracts, insurance and records where appropriate to manage operational exposure.
04 — Compliance
Review private benefit, inurement, valuation, related-party and tax issues before execution.
05 — Lawful value flow
Transfers involving the Foundation must be structured to support lawful exempt purposes and avoid prohibited private benefit or inurement.
06 — Evidence
No material ownership, lease, license, sale, service or funding relationship should rely solely on an informal understanding.
Federal tax note: the IRS states that a 501(c)(3) organization must operate for exempt purposes and may not allow net earnings to inure to private shareholders or individuals. Related organizations and controlled entities can also create reporting and tax considerations, including transactions involving rents, royalties, interest, loans or fund transfers. Actual treatment depends on the entities, documents and facts as implemented.
E. Transaction Gate
One control cycle across every layer.
01Initiate
02Verify Authority
03Value / Allocate
04Approve
05Execute
06Record
07Reconcile
08Review
F. Architecture Registers
Connect the hierarchy to the documentary record.
| Register | Purpose | Primary Control | Status |
|---|---|---|---|
| Master Entity, Asset & Transaction Schedule | Maps assets, activities, holders, proposed entities, revenue/expense ownership and required agreements. | Verify → Approve → Execute → Reconcile | WORKING |
| Transaction Matrix & Inter-Entity Agreement Register | Defines recurring transfers, services, PMA interfaces and documentary requirements. | Authority + agreement + accounting trail | WORKING |
| Enterprise Structural Charter | Defines the intended hierarchy and separation of Foundation, management, asset-holding, operations and PMA interface. | Board adoption + executed legal documents | WORKING |