Master Schedule Extension

PMA Asset, Function & Transaction Addendum

A controlled extension of the Master Entity, Asset & Transaction Schedule for SovereignAqua Imperium-Habour PMA. It identifies the PMA's proposed functions and interfaces without converting those proposals into evidence of ownership, tax status, legal authority or completed transactions.

Boundary rule: The PMA is treated here as a separate proposed private-membership / enterprise platform. It is not presumed to be owned, controlled, operated or tax-exempt through the SovereignAqua Foundation. Any relationship must be established by executed formation, governance and contractual documents.

Verify

Confirm the PMA's jurisdiction, formation status, governing documents, authority and signatories.

Document

Identify the exact asset, service, right, funding or obligation and the instrument governing the relationship.

Reconcile

Match contracts, invoices, asset records, project records and accounting entries after execution.

PMA Register

First-class PMA participation schedule

These rows extend the master architecture. “Proposed,” “Open” and “Verify” are control statuses, not completed legal events.

ID	PMA Function / Asset	Current / Proposed Holder	Counterparty / User	Legal / Contractual Basis	Transfer / Interface Method	Revenue Owner	Expense Owner	Required Document	Status
PMA-001	Research & innovation projects	PMA / verified research rights	Foundation or appropriate research entity	Executed authority + R&D terms	Research agreement / work order	Per executed agreement	Per executed agreement	R&D Agreement + approved scope/budget	VERIFY
PMA-002	Intellectual property / know-how	Verified IP owner	PMA or licensed entity	Ownership record + license/assignment authority	License / assignment	IP owner, subject to agreement	Licensee / assignee	IP Assignment or License	VERIFY
PMA-003	Technology / software / technical know-how	Verified owner or PMA where lawfully owned	Operating / research entity	IP ownership + services authority	Technology license / services	Per agreement	Receiving entity	Technology License / Services Agreement	OPEN
PMA-004	Membership programme and contractual rights	PMA	PMA members / participants	PMA governing documents + membership terms	Membership enrollment / service terms	PMA, subject to governing documents	PMA	Membership Agreement / Terms + privacy documentation	OPEN
PMA-005	Management / administrative / technical services	PMA or service provider	BWC / operating entity	Services authority	Services agreement + invoice	Service provider	Receiving entity	Shared Services / Services Agreement	OPEN
PMA-006	Facility / equipment / infrastructure use	Verified asset owner	PMA	Title + permitted use	Lease / license / asset-use agreement	Asset owner where consideration applies	PMA	Facility / Asset Use Agreement	VERIFY
PMA-007	Financing / capital deployed to PMA	Lender / investor / capital source	PMA	Executed financing authority	Loan / investment / capitalization	Per financing documents	PMA or responsible borrower	Capital / Loan Documents	VERIFY
PMA-008	Procurement and vendor contracting	PMA	Vendor / contractor	Procurement authority	PO / vendor agreement	Per commercial arrangement	PMA	Purchase Order / Vendor Agreement	OPEN
PMA-009	Foundation programme support to PMA	Foundation, if legally authorized	PMA / approved programme	Exempt-purpose authority + grant/service terms	Grant / R&D / service agreement	Per agreement	Per agreement	Grant or Programme Agreement + budget	CONDITIONAL
PMA-010	PMA use of Foundation-controlled resources	Foundation / controlled entity	PMA	Specific authorization + permitted use	License / service / asset-use agreement	Per agreement	PMA or user entity	Asset Use / License / Services Agreement	CONDITIONAL

Control Requirements

Every PMA interface must answer eight questions.

01 · Who has authority?

Identify the legal entity, governing body and authorized signatory.

02 · What is moving?

Identify the asset, service, IP, funding, membership right or other value.

03 · Why is it permitted?

Record the governing law, formation document, resolution or contract that authorizes it.

04 · What is the consideration?

State price, valuation, fee, allocation, grant restriction or other economic basis.

05 · Who records it?

Assign revenue, expense, asset, liability and project accounting responsibility.

06 · What agreement governs?

Assign a document ID, effective date, version and retention location.

07 · What compliance gate applies?

Review tax, nonprofit, private-benefit, related-party, regulatory and jurisdictional issues as applicable.

08 · How is it reconciled?

Match the executed document to the operational record and accounting entry.

Implementation rule: A PMA transaction must not be represented as a Foundation transaction merely because the parties share a mission, brand, personnel or programme. If the Foundation is a U.S. 501(c)(3), related-organization and controlled-entity reporting may also become relevant depending on the actual relationship and transactions.

Return to Master Entity, Asset & Transaction Schedule · Open PMA Enterprise Interface Register · Open Transaction Matrix