1XP
1XP Gov
Terra #4857 11/24/2026, 2:25:58 PM

Community governance and independent Foundation accountability

Terra proposal #4857: # Proposal 2 — Community governance and independent Foundation accountability In this proposal, **PD** means the Phoenix Foundation and...

Yes

100%

No

0%

Abstain

0%

Veto

0%

If passed

No machine-readable execution payload was received. The effects are unknown; the description alone cannot confirm that nothing will execute.

Original Proposal Text

# Proposal 2 — Community governance and independent Foundation accountability In this proposal, **PD** means the Phoenix Foundation and its relevant PD Stewardship officeholders. This proposal can operate with the existing directors if Proposal 1 fails. It removes no named director and grants no 2-of-3 permission. ## Decision requested Approve the exact prospective bylaw changes in Appendix A, lawful alignment of the Foundation's governing instruments, a neutral financial and authority review, and consistent conflict controls for all directors. The purpose is accountable community direction over Foundation affairs while preserving the legal responsibilities, private rights and execution safeguards that cannot lawfully be overridden. A binding decision requires implementation within the Foundation's lawful authority. It does not require directors to carry out an unlawful act or breach a non-waivable duty. Directors must assess a specific legal or execution obstacle case by case under Article 1.11.5, disclose the affected act and reasons, obtain independent assessment through the approved route, and pursue a lawful remedy while continuing unaffected work. This preserves necessary judgment without creating a general discretion to disregard a passed decision because the Board disagrees with its policy. The community decision and legal adoption are distinct events. The proposed final-authority rule does not supply the authority to adopt itself. Until adoption is completed, existing documents and legal requirements remain controlling. The proposed ordinary-governance rule neither declares an emergency nor revives rejected emergency-supervisor proposals. ## 1. Post-vote directions to PD and lawful adoption The "Passage Date" is the date this proposal is recorded as finally passed on chain. From that date, PD is directed to start implementation work within its existing lawful authority and publish progress weekly. Within 21 calendar days of passage, publish an implementation dossier covering the governing instruments, adoption and enforcement route, review arrangements, contract schedule, funding and completion dates specified in Sections 1–3. The Board is responsible for coordinating the response with relevant records custodians and publishing the responsible implementers. This community reporting deadline starts at passage and does not wait for bylaw adoption, counsel or a preferred set of records. If an item is unavailable, identify its custodian, the request made, the exact gap, next action, responsible person and dated completion plan. Missing material is not deemed supplied. Within seven calendar days of passage, PD must publicly acknowledge the passed decision, name the responsible implementers and confirm that it will comply with the mandate through the applicable lawful procedures and provide the required documents and implementation response within 21 calendar days of passage. The acknowledgement records the community decision; it is not a second approval or an opportunity to reopen its merits. Late or withheld acknowledgement does not postpone or restart the 21-day deadline. A specific legal or technical obstacle must be identified and handled under the reporting and referral procedure below, with unaffected work continuing. Publish the effective Charter, later amendments and relevant participation/authority agreements, or an authorized explanation of a publication restriction with the operative provisions made available for independent verification. Identify the precise provisions requiring amendment, exact replacement text, competent approvers, current signing thresholds, vetoes, required consents and filing/notice requirements. Seek independent Cayman advice on compatibility with applicable duties and the existing dispute process. An unproduced instrument must be identified, requested and reported under the implementation process. Seek an independent adoption/enforcement coordinator, counsel and alternate, and publish their proposed scope, acceptance, independence disclosures and quotations. Identify persons with legal standing, records-access arrangements and the legal funding route. Consider the standing Supervisor, secretary or other competent office according to actual powers; community designation alone does not confer them. Identify the route if incumbents refuse necessary signatures, including applicable Article 7.2 notice/arbitration steps and any competent court remedy. No judicial outcome or substitute signing power is assumed. PD may obtain records, request quotations and perform preparatory work within existing authority. Paid engagements may proceed only within a specific existing valid budget and approval route that covers them, with the required disinterested approvals. This proposal appropriates no unspecified amount and authorizes no unfunded commitment. Where further funding or appointment approval is needed, PD must publish the proposed provider, scope, amount or cap, duration, funding source and approval route within the same 21-day period and promptly put the specific request to the competent approver, including Terra Governance where required. Missing funding does not suspend records disclosure, available preparatory work or weekly reporting. The 21-day dossier must also identify the lawful contingency for too few disinterested signers, refusal to execute, or resignations or disqualifications leaving fewer than three directors. State the existing authority, authorized actors and necessary approvals. If no such route is available, disclose the precise missing authority and promptly seek the specific further approval; do not invent a lower quorum or suspend an existing duty to resign. The dossier is an implementation record produced after passage, not an undisclosed document incorporated into this vote. It may identify factual details and conforming execution steps within the approved policy. It may not change the allocation of power, expenditure authority, review scope, thresholds, safeguards or deadlines. Publish its dated versions and exact instruments before use. A material departure or additional authorization requires a fresh express governance decision and applicable legal approvals. Authority to prepare implementing documents does not authorize a different constitutional settlement. Continue implementation steps that do not depend on a further approval. PD must promptly pursue valid adoption of the exact Appendix A amendments through the existing instruments. The new bylaw duties take legal effect only upon valid adoption of the instruments that make them operative (the "Adoption Date"). The adopted instruments must expressly give the resolution obligations and Appendix A their intended legal effect and identify the persons bound. The Adoption Date is the objectively evidenced completion of the last condition required for those instruments to take effect, subject to independent verification and any competent authority's jurisdiction. Publish the evidence and exact date promptly; delayed publication does not change the event or restart a clock. Until adoption, the post-passage directions are the community's mandate to PD to act through its existing powers. Amendments and contracts take legal effect through their applicable adoption and execution procedures. The independent review and funding must use valid engagement instruments and cannot use the proposed new powers to authorize themselves. The Passage Date reporting mandate remains applicable throughout. An incomplete reviewer appointment or funding process does not postpone adoption of otherwise valid amendments or other unaffected work. Identify a genuine dependency on the affected act specifically. From passage, PD is also directed to follow the reporting, assessment and referral procedure in Appendix A Articles 1.11.5 and 1.11.7 through existing lawful authority. Pending an independent appointment, the Board must publish requests for assessment and notify the standing Supervisor and secretary within their existing remits. At a 21-day assessment deadline, publish the independent assessment or provisional assessment if available; otherwise publish the missing appointment or funding, requests and quotations, proposed lawful next step and dated completion plan. A Board status report is not an independent assessment and does not discharge the open obligation. Withholding a notice, referral or records does not postpone the deadline. ## 2. Independent financial and authority review Within 21 calendar days of passage, PD must seek and publish independent reviewer candidates or a proposed firm/team, qualifications, independence disclosures, written availability or acceptance, proposed engagement terms, quotations, cost cap, funding source and lawful appointing/payment route. Directors and funded projects under examination may supply records and request quotations but may not decide the reviewer's substantive selection, findings, publication, dismissal or fee releases. Use an existing competent, disinterested appointing authority where available. Otherwise put the reviewer and bounded engagement to Terra Governance for express selection and obtain any required legal approvals. Any legally unavoidable formal execution by incumbents must be distinguished from those discretionary powers. Publish any absence of a lawful independent arrangement and the proposed remedy; do not invent an office with no authority. Pursue appointment promptly under existing lawful authority; adoption of the new bylaws is not a reason to delay an otherwise authorized engagement. The target is appointment no later than seven calendar days after the Adoption Date. If a specific funding or appointment approval remains outstanding, publish it and pursue the Section 1 approval route; do not incur an unauthorized commitment or silently reset the target. The engagement must protect independent access to records and direct publication of authorized findings; neither favorable findings nor consent from subjects may condition payment or publication. Removal requires documented cause, an independent determination and an accepted replacement under the same approved process, with preservation of work and funds. Publish conflicts, decisions and reasons. The reviewer receives no power to sign Treasury transactions, seize assets, remove directors or exercise Emergency Supervisor powers. The review covers Foundation-controlled funds and authority and relevant predecessor TLA commitments from the published TLA launch commitment dated 12 August 2024 through the Passage Date. Include earlier agreements only where necessary to establish opening balances, continuing obligations or authority relevant to that period, and subsequent transactions only to verify implementation or resolution of an in-scope item. PD must publish the corresponding block/date boundaries and entity/contract inventory within the 21-day implementation response; those factual particulars may not narrow the approved scope. Follow assets and counterparties only to the extent necessary to reconcile that scope. Do not imply an unlimited examination of unrelated private businesses. Preserve relevant records from passage, including off-chain agreements and acceptance records; publish a record-request index and report access denials. The approved access route must cover private documents lawfully, without publishing identity documents, keys or privileged advice. Reconcile approved funding, actual transfers and ultimate recipients where verifiable, paid versus conditional amounts, milestone acceptance, fees and commissions, Treasury investments, liquidity positions, lending collateral, and identified claims and liabilities. Review privileged contract operations against the authority, disclosures and approvals applicable when they occurred. Count each economic transfer once and show internal transfers, refunds, overlapping grants and investment positions separately. Publish the complete in-scope transaction/authority population and explain which items receive detailed testing, the selection method, materiality, excluded records and confidence limits. Distinguish the reviewer's own testing from earlier published analyses. Sampled testing must not be represented as an independent audit of every transaction. Apply the same questions and evidence standards to decisions involving every director and funded team in scope, including decisions critical of or supporting any director. A recorded payment is not proof of personal profit or non-delivery. Approval for continued service, approval of a grant, milestone acceptance, payment execution and actual receipt are distinct events. Consider contemporaneous explanations and test delivery claims; subsequent website captures alone do not establish that work was not performed. Publish preliminary findings within 30 calendar days and a final report within 60 calendar days of the Adoption Date, not appointment or receipt of a preferred set of records. Before adverse findings are finalized, give affected parties the relevant evidence and at least seven calendar days to respond; a fair opportunity may require reporting an item as unresolved at day 60. The day-60 report must identify established facts, disputed matters, unavailable evidence and further work rather than manufacture certainty or silently extend scope. If appointment, funding or access prevents an independent report at either deadline, PD must publish the exact outstanding item, requests and approvals sought, work completed, responsible person and dated remedy. Such a status report is not an independent review or satisfaction of the reporting obligation. The item remains open, with weekly progress reporting and any further timetable or funding approval made expressly. Any additional funded phase requires specific approval with a cap and deadline; findings may be corrected publicly with a dated explanation. For each discrepancy, publish the response, analysis, recommended corrective act and the authorized decision on whether to pursue recovery or enforcement. Qualified counsel assesses legal remedies, limitation periods, standing, costs and contractual rights; the reviewer does not declare automatic clawbacks. Preserve rights and evidence while the competent body decides. Identify who must act, its deadline and any unresolved obstacle. No historical conduct is evaluated as a breach of a new rule that was not in force at the time. ## 3. Conflicts, commitments and public accountability Within seven calendar days of the Adoption Date, every current director must publish ongoing material financial conflicts, dated disclosures previously supplied to both Board and community, the disinterested-director approvals for continued participation under existing §4.6.2 and their conditions. This covers project ownership, paid roles, validator operations, commissions, protocol fees and other material economic relationships relevant to Foundation decisions. Publish missing records as missing, and supply protected material lawfully to the reviewer. Provide a response opportunity before an adverse compliance conclusion. Subsequent disclosure or approval is not proof of historical compliance or retrospective absolution. Apply §4.6.2 according to its actual awareness, ongoing-material-conflict, disclosure and majority-of-disinterested-directors conditions, including its resignation requirement where applicable. Participation approval is distinct from transaction approval. New grants, fee increases, Treasury allocations and payment amendments benefiting a director or related business require the new public declaration, justification and independent approval controls in Appendix A once validly adopted. Beneficiaries may not approve their budgets, milestone acceptance or releases. Preserve enforceable obligations and independent approval of bounded essential-service arrangements; resolve insufficient disinterested signers through the actual lawful contingency, not a reduced numerical minimum. Preserve the original TLA administration-after-one-month and ownership-after-three-month commitments in the [launch document]. They concern specified contract powers, not automatic title to all ERIS infrastructure. This proposal neither waives those commitments nor retrospectively approves departures, and it does not adjudicate contested enforceability. Any variation requires its exact scope and applicable separate approvals. A claim of private ownership alone does not resolve a promised transfer. Within 21 calendar days of passage, PD must publish a contract/control schedule identifying chain/address, code/version, migration administrator, internal owner, controllers, pending transfers, role-granting and upgrade powers, current holder with evidence block/time, direct and indirect control paths, intended successor, original commitment or other transfer basis, required transactions/acceptances, dependencies and verification tests. Identify missing entries under Section 1's reporting rule. Distinguish historical captures and unresolved attribution from verified current state. Verify completed transfers through published transactions and independent post-change checks for any retained direct or indirect privileged route to restore or override the authority without fresh authorization. Credit completed handovers and publish the unfinished scope. The schedule, independent access and review appointment must serve this mandate if Proposal 1 fails; no mutable reference to that proposal supplies or changes the approved scope. The same 21-day schedule must explicitly cover TLA global configuration and the Treasury and v3 contracts used by the Foundation, where applicable. Trace who can change owners, administrators, role grants, fee settings, asset destinations or upgrade permissions, including through shared configuration contracts. Identify retained privileged control and its basis; a transfer of one local role is not evidence that upstream control has also transferred. Inventorying a contract does not establish a right to take ownership of it. For each in-scope deployment, record the matching source repository and commit, deployed code identifier and checksum, build instructions and toolchain, licence, operating documentation and maintenance dependencies. Identify whether the Foundation and an independent replacement operator have the access and rights needed to inspect, reproduce, maintain and, where authorized, upgrade it without continuing dependence on the outgoing provider. Publish materials where rights permit; explain restrictions and provide lawful independent verification of protected material. A missing public repository alone does not establish what rights or access exist. Distinguish existing delivery obligations from any new licence or service that would require negotiation and separate approval. Before reporting software handover or independent operating readiness complete, publish the independent verifier's build and operational checks and any unresolved dependency. This is a separate milestone from director removal and permission-transfer transactions. Within the same 21-day period, publish a costed contingency plan for unavailable cooperation, code, permissions or operating support. Compare feasible continued operation, replacement operators, migration and orderly withdrawal options; identify Treasury and user-fund exposure, dependencies, costs, funding, timescales, approvals and service risks. If an option is not yet costable, identify the missing evidence and a dated plan to obtain it. Explain whether any option would require reconsidering the Alliance or its incentives. Put any proposed material change to Treasury exposure, custody, protocol arrangements or Alliance incentives to Terra Governance with its exact scope and required lawful approvals. This planning direction authorizes no automatic withdrawal, shutdown, incentive change, new commitment or waiver of an existing handover claim. Continue unaffected implementation and weekly reporting. Where Proposal 1 separately applies, this planning duty does not postpone its removal process or extend its temporary authority. The Board must maintain the public decision register and circulate an accountability report every four calendar months under Article 1.11.9. Reports must cover Board and community decisions, approvals, commitments, payments, milestone acceptance, conflicts and recusals, implementation status and unresolved earlier decisions. They supplement weekly implementation updates and prompt disclosure of material obstacles. Under Article 1.11.10, publish a proposed framework for Board versus Terra Governance approval within 60 calendar days of the Adoption Date, allow at least 21 calendar days for public comment, and submit the exact proposed framework to Terra Governance within 90 calendar days of the Adoption Date. It must distinguish routine execution within an approved mandate from decisions requiring a separate community vote, using financial exposure, purpose, duration, conflicts and control risk as well as spending amounts. Related awards and commitments must be assessed together to prevent splitting. This proposal sets no new spending threshold or expanded delegation before the framework is expressly approved and lawfully implemented. ## 4. Deadlines and independence of the votes For this proposal, PD must **acknowledge passage within seven calendar days**, name the responsible implementers and confirm compliance and delivery of the required documents and implementation response **within 21 calendar days of passage**. Both deadlines run from passage. Acknowledgement does not restart the clock or provide a second policy approval. The standing rule in §1.11.4 likewise requires acknowledgement within **seven calendar days** and implementation and supporting documents within **21 calendar days of passage**, unless the decision specifies another timetable. Where objectively necessary legal or technical prerequisites prevent completion, publish the evidence, outstanding steps, responsible implementers and a dated completion timetable within that same 21-day period. Disclose material obstacles promptly and continue unaffected work. Articles 1.11.5 and 1.11.7 use a **21-calendar-day assessment and escalation period**, with prompt referral and no successive extensions for assessment and legal escalation. That period does not extend the implementation deadline. The specific seven-day appointments/disclosures, 30/60-day review reports, four-calendar-month reporting cycle and 60/90-day delegation-framework timetable above are express exceptions. The public-comment period for that framework is at least 21 calendar days. #4855's existing specific deadlines remain unchanged. Adoption of this proposal cannot reset another validly applicable clock. If Proposal 1 fails or is not adopted, this proposal creates no removal direction or temporary threshold. If Proposal 1 is separately adopted, its approval requirement, restrictions and 60-day discretionary spending limit remain intact. A general duty to implement governance decisions cannot be used to enlarge a restricted interim mandate: a further decision must expressly identify and approve that change and receive required legal adoption. A financial or review obligation common to both proposals is performed once with shared evidence and reconciled costs; the earlier applicable deadline controls and no fee is charged twice. YES approves the exact bylaw amendments, governance-and-accountability policy, review scope, safeguards and post-passage directions in this text, irrespective of the outcome of Proposal 1. It does not approve an unseen future dossier, unspecified expenditure or an alternative constitutional settlement. NO rejects this package; it neither approves misconduct nor removes existing bylaw duties, handover rights or #4855. ABSTAIN and NO WITH VETO retain ordinary Terra effects. Splitting the votes allows independent choices; it does not turn either text into a self-executing legal instrument. [launch document]: https://github.com/phoenix-directive/docs/blob/7cebbd26048f0e1568a2aed55177090b90788d8b/common_backup/2024-08-12_24385_launching-terra-liquidity-alliance.md ## Appendix A: Proposed bylaw amendments These amendments are part of the proposed YES resolution. They take effect only after the required adoption steps. Terra Governance has the final say over Foundation governance within the Foundation's lawful authority. The Board must implement passed ordinary and emergency decisions, subject to the specific legal and execution safeguards in Article 1.11.5, without a second discretionary policy approval. Adopt the replacements and additions below as one package. References are to the [published Phoenix Foundation bylaws][bylaws], adopted on 22 December 2025. The adoption record must identify this proposal's assigned on-chain ID and preserve an immutable copy of this schedule and the election procedure approved in proposal 4855. Initial adoption must follow the **existing** §7.3, effective Charter and applicable approvals. Obtain any required constitutional amendments and agreement changes; publish their exact text and adoption evidence. A governance vote alone does not establish that those steps have occurred. Sections 7, 9, 10 and 12 of the [Cayman Foundation Companies Act][act] are relevant: the constitution can allocate governance powers, constitutional changes have their own requirements, and bylaws operate subject to the constitution and law. This schedule does not purport to override mandatory law, court orders or protected third-party rights. **1. Replace §1.4.1 with:** > **1.4.1 Community mandate.** The BORG shall act in accordance with the Phoenix Directive and the binding decisions of Terra Governance under Article 1.11. Terra Governance is the BORG's highest governance authority within its lawful remit and subject to Article 1.11.5. The Board and other BORG Personnel exercise delegated authority subject to those decisions. **2. Insert §1.11:** > **1.11 Final authority of Terra Governance.** > > **1.11.1 Binding decision.** A Binding Governance Decision is a proposal recorded as finally passed by the Cosmos SDK governance module on the Terra blockchain, under its applicable voting requirements, whose operative text expressly directs, approves, prohibits, amends or reverses a specified matter concerning the BORG, its affairs or assets and rights within its lawful control. This prospective rule applies to decisions finally passed on or after the Adoption Date. The only earlier decisions newly carried forward by this package are this proposal, #4855 and Proposal 1 to the extent separately passed and validly adopted. Record their immutable text, outstanding acts and applicable timetables in the adoption schedule; that record cannot add another earlier decision or enlarge an approved mandate. Bringing any other historical decision within this new rule requires fresh express Terra Governance approval and any applicable legal adoption. No historical vote acquires a new retrospective deadline or finding of breach. Existing independently binding obligations and their deadlines remain unaffected. Both executable and non-executable proposals may qualify; an expressly non-binding consultation does not. A reference to a document does not incorporate later edits. Preserve the final passed text, immutable incorporated documents, proposal ID, result and scope in the BORG records. A material ambiguity, inconsistent instruction or attempted action outside lawful authority follows Article 1.11.5; it is not permission to select a preferred policy privately. > > **1.11.2 Reserved final authority.** Terra Governance has the final governance decision over the BORG's mandate; director selection and removal; Board size and voting thresholds; Bylaws and governance procedures; budgets, Treasury and Ops Fund policy and specifically directed expenditures; delegation and custody of Foundation authority; and the scope, appointment and removal of oversight roles, subject to Article 1.11.5. A director, Board majority, multisig, Supervisor, Emergency Supervisor, committee, contractor or operator has no independent policy veto over a Binding Governance Decision. > > **1.11.3 Implementation, not reconsideration.** The BORG and BORG Personnel shall perform the corporate acts, signatures, appointments, removals, transfers and other actions within their authority needed to implement a Binding Governance Decision. Any Board or multisig resolution, ratification, acknowledgement or execution required for implementation is an implementation duty; it is not a second discretionary decision on the merits. Opposition to the proposal, absence from its vote, concern about the proposer's motives, or disagreement with its policy does not excuse non-performance. No individual shall be required to sign a transaction that differs materially from the approved decision or is subject to Article 1.11.5. > > **1.11.4 Deadlines and publication.** For decisions within Article 1.11.1, unless the decision specifies another timetable, publicly acknowledge the passed decision within seven calendar days of passage, name the responsible implementers and confirm that the BORG will comply through the applicable lawful procedures and provide the required implementation and supporting documents within 21 calendar days of passage. Implement without undue delay and within that 21-day period, and publish the completed acts and supporting evidence. The acknowledgement records the community decision; it is not a second discretionary approval. Late or withheld acknowledgement does not postpone or restart any deadline. Where objectively necessary legal or technical prerequisites prevent completion within the 21-day period, publish within the same period the completed steps, outstanding acts, specific prerequisites and supporting reasons, responsible implementers, and a dated completion timetable. Disclose material obstacles promptly upon identification, continue unaffected work and publish weekly updates until completion. Any claimed obstacle remains subject to Article 1.11.5; a completion timetable may allow only the time reasonably necessary to resolve the obstacle and execute the affected act. Resume affected implementation promptly when the obstacle is resolved. Publishing a timetable does not discharge the implementation obligation, authorize indefinite delay or restart the original clock. For expressly carried-forward earlier decisions, the adoption schedule shall identify the applicable existing timetable or expressly approved prospective timetable; it cannot silently reset an existing deadline or retrospectively create a breach of a new duty. No BORG body may create unnecessary prerequisites, restart completed stages or withhold documents to defeat a decision. > > **1.11.5 Specific legal or execution obstacle.** No act is required that would breach applicable law or a non-waivable duty, the effective constitution, a binding court order, an enforceable third-party right, solvency restrictions, or correct and safe transaction execution. Directors must continue exercising the judgment required to identify those constraints. Pause only the affected act for the time reasonably necessary to resolve the specific obstacle. Identify the legal provision or concrete technical defect and disclose the obstacle promptly. The adopted enforcement coordinator must promptly refer it to the retained independent assessor. Within 21 calendar days of identification, publish an assessment or a provisional assessment specifying missing evidence and next steps, an authorized summary, the proposed remedy and timetable, protecting privileged material, personal information and exploitable security details. Within that same period, refer any unresolved obstacle and proposed lawful remedy to Terra Governance and the person with standing to pursue the required corporate, contractual, arbitration or court process; where a legal remedy is required, instruct the retained independent Cayman counsel through the approved route. Withholding notice, referral or records, or delivering a late assessment, does not postpone these concurrent requirements. If an earlier deadline applies under Article 1.11.7, it controls. Publish any unavoidable assessment delay and use the accepted alternate where needed. A disagreement with policy alone is not an identified legal or execution obstacle. A required constitutional change must be pursued through its competent process. A missed deadline alone is not a finding of bad faith. No deadline requires an unlawful act, and this assessment period does not itself extend an implementation deadline. A report alone does not discharge the implementation obligation. > > **1.11.6 Priority and ordinary business.** Final community authority over a subject does not by itself require a separate vote for every routine act within an existing lawful delegation. Prior express community approval is required where these Bylaws or a Binding Governance Decision expressly require it, including director selection, discretionary removal, Board-size or signing-threshold changes and substantive bylaw amendments. Ordinary oversight administration otherwise remains with its competent body, subject to express community decisions and the selection, replacement and independence safeguards of adopted engagements. This Article governs the interpretation of all other Bylaws, including Articles 1.2.2, 1.10, 2.4.3.1, 2.4.5.4, 3.1.1, 3.2.1.5, 3.2.5, 4 and 7.3. Internal policies and arrangements shall be brought into conformity through the necessary lawful approvals. Ordinary business that Terra Governance has not reserved or decided remains delegated under the applicable budget, signing threshold and controls. Article 1.11.10 requires an expressly approved framework to make that allocation clear; preparing it grants no additional authority. Governance silence is not approval of an action requiring an express vote. Later Binding Governance Decisions prevail over earlier ones only to the extent of an express change or irreconcilable conflict; seek clarification of a material ambiguity and continue unaffected work. > > **1.11.7 Compliance and enforcement.** Promptly publish a missed-deadline notice identifying the unfinished act, responsible officeholder, specific obstacle and proposed remedy. Continue unaffected work. The standing Supervisor shall receive reports and seek explanations within its established powers; this Article does not designate it an Emergency Supervisor, automatically give it keys, or assume it can replace a missing signature. A missed implementation deadline triggers independent assessment whether or not a notice is published. The enforcement coordinator must promptly refer the unfinished act to the retained independent assessor and transmit available records. Within 21 calendar days after the missed deadline, publish an assessment or specific provisional assessment and refer any unresolved refusal or obstacle requiring a legal remedy to independent Cayman counsel through the approved route, with an authorized explanation of the next step and timetable. Where an obstacle was identified earlier, the earlier Article 1.11.5 deadline controls. These are concurrent requirements: a withheld notice, delayed referral, missing record or overdue assessment does not postpone either obligation. The assessment period does not extend the missed implementation deadline. If an independent appointment or valid funding is unavailable, the Board must publish the missing item, appointment and funding requests, quotations or refusals, proposed lawful next step and dated remedy by the same deadline. That status report is not an independent assessment or discharge of the obligation. Apply this fallback also to Article 1.11.5, promptly notify the standing Supervisor and secretary within their existing powers, and pursue the lawful appointment and funding route. Preserve the Charter, applicable Article 7.2 dispute processes, contractual rights and the competent jurisdiction of courts. An authorized person with legal standing must instruct and fund each proceeding through the approved route; community designation alone supplies neither. Terra Governance may approve a specific lawful remedy or change of implementer. No unspecified chain intervention, seizure, private-key takeover or unlimited legal expenditure is authorized. Publish the independently approved engagement, caps, access rights, alternate and publication duties in the implementation record; a material change requires the applicable approvals and cannot alter the community-approved mandate without express further approval. > > **1.11.8 Independent protocols, commitments and Foundation funds.** Terra Governance authority under these Bylaws concerns the BORG, its Personnel acting in that capacity, and assets and rights within its lawful control. It does not create ownership of independent infrastructure. Nothing in this Article waives, releases or retrospectively approves a departure from published handover commitments or associated rights and obligations. A description of infrastructure as independently owned does not determine whether specific administration, configuration or other permissions were committed for transfer. Any proposed variation must identify the affected contracts, permissions, assets, reasons, original commitment and exact change, and receive separate express approval through the applicable governance and legal procedures. Identify any asserted prior variation and its adoption evidence; preserve disputed claims for proper determination. The Foundation shall separately approve the terms of Treasury exposure, fees, reporting, withdrawal, exit and administrative protections through the applicable Treasury and governance procedures. Investment alone does not establish ownership, and this Article authorizes neither new exposure nor return of Foundation authority to a third party. > > **1.11.9 Public decisions and periodic accountability.** The Board shall maintain a public register of Foundation Board decisions and Terra Governance decisions concerning the Foundation, and their implementation. Record the decision and authority, date, approvals, amounts committed and paid, recipient or counterparty, milestone-acceptance evidence, relevant conflicts and recusals, responsible implementer, status, outstanding act, reason for delay and next dated step, as applicable. Link supporting records and protect information under Article 5.2. Update the register within seven calendar days of a decision or material status change, subject to any earlier disclosure duty. The first consolidated report is due within four calendar months of the Adoption Date, with subsequent reports due at successive four-calendar-month intervals from that date. Publish and circulate each report through the Foundation's public community channels, covering the period and unresolved earlier decisions. Late publication does not reset the schedule. Historical inclusion records status; it does not extend Article 1.11.1 to additional historical decisions or invent a retrospective breach. Periodic reports supplement prompt material disclosures, weekly implementation updates and independent reviews; they do not replace them. > > **1.11.10 Delegation and reserved-decision framework.** Within 60 calendar days of the Adoption Date, the Board shall publish a proposed framework identifying decisions it may approve under lawful delegation and decisions requiring prior express Terra Governance approval. Allow at least 21 calendar days for public comment and submit the exact proposed framework, with responses to material comments, to Terra Governance within 90 calendar days of the Adoption Date. The framework must specify budget and project limits, purposes, duration, reporting, milestone acceptance, disinterested approvals, and escalation rules. It must distinguish grants and operating expenditure from Treasury investments, loans, guarantees and liquidity commitments, and assess total financial exposure, custody, upgrade and administrative control, fee changes, related-party benefits and strategic significance. Assess related awards, renewals and commitments to the same project or related counterparties together; splitting must not evade a limit or required vote. The framework must identify its aggregation periods, valuation method, thresholds and treatment of budget changes expressly. A monetary amount alone does not determine authority. Existing reserved decisions and stricter safeguards remain controlling. Pending express community approval and lawful implementation, existing lawful delegations continue within their limits; this Article grants no new spending power, exemption or authority to exceed them. A material change to the approved framework requires further express Terra Governance approval and lawful implementation. **3. Replace §7.3 with:** > **7.3 Amendment; Waiver.** Following valid initial adoption of this Article, every substantive amendment or waiver of these Bylaws requires prior express approval by Terra Governance of the exact amendment or waiver, its scope and any duration. The Board and Stewardship Multisig shall complete any legally required adoption or execution acts under Article 1.11 without a further discretionary veto. Neither body may substitute materially different text. No Board policy, side agreement, emergency designation or purported interpretation may waive or weaken Terra Governance's final authority. Any corresponding constitutional amendment must follow the constitution's lawful amendment process. Publication, recordkeeping and purely clerical corrections may be made without another vote only where they change no right, duty, power, threshold, deadline or substantive meaning; publish their diff and explanation. This Article does not retrospectively dispense with the approvals required to adopt this amendment package. **4. Replace §2.2.2 and §2.2.3.2; replace §2.4.2.2; amend §2.4.3.1 as specified:** > **2.2.2 Number of Directors.** The approved target is five equally weighted directors under proposal 4855. Terra Governance determines a change to that target through express approval and the required lawful implementation. This Article authorizes no reduction in membership or signing threshold. Configurations with three, four or five serving members require at least three affirmative approvals following valid adoption and the tested corresponding configuration update. Existing technical authorizations remain operative until lawfully changed. No two-member governance is authorized. A change in actual membership does not permit incumbent selection of replacements or suspension of the approved elections. > > **2.2.3.2 Subsequent Directors.** All subsequent directors, including replacements, additional seats and temporary or interim appointments, shall first be selected through the public nomination and on-chain election procedure approved in Terra governance proposal 4855, or a replacement procedure expressly approved by Terra Governance. Preserve an immutable copy of that procedure with these Bylaws. Community selection determines who is to be appointed, subject to objective eligibility and onboarding. The Board shall complete the appointment and corresponding multisig update under Articles 1.11 and 2.4.3.1. It may not substitute its own nominee, impose a political-alignment test or require a second discretionary approval of the selected candidate. Multiple seats shall be filled through separately identified, sequential elections under the approved procedure. > > **2.4.2.2 Subsequent Stewardship Multisig Members.** Appoint the community-selected eligible director under Article 2.2.3.2 by executing the required multisig membership update. This implements the selection and does not constitute a separate election by incumbent members. Retain the documentary and legal eligibility requirements in §2.4.3.1. Replace its concluding paragraph authorizing a veto by inaction with: > A candidate may be held pending only for a specifically identified, unsatisfied eligibility or onboarding requirement under Articles 2.1 or 2.4.3.1 or applicable law, subject to Article 1.11.5 and the published candidate-response and independent-review procedure. Publish the requirement, responsible reviewer and remedial timetable. Apply the same requirements to all candidates. Foundation-caused delay is not candidate refusal or ineligibility. A genuine failure of eligibility shall be handled under the approved election procedure, including its successor and reopening rules. An incumbent's preference or inaction does not constitute an additional appointment condition. **5. Replace §2.2.6 and §2.4.4.1; replace §2.4.5.4:** > **2.2.6 Removal of Directors.** Terra Governance may direct the removal of a named Director, with or without a finding of misconduct, through a Binding Governance Decision. The BORG and its Personnel shall perform the acts necessary to give that decision legal and technical effect under Articles 1.11 and 2.4.4.1. Incumbent Directors have no discretionary veto over the removal. Resignation, death and a removal or disqualification required by mandatory law or a binding court order remain effective through their applicable procedures. Removal from office does not itself adjudicate damages, extinguish earned contractual rights or impose a criminal or civil penalty. > > **2.4.4.1 Removal from the Stewardship Multisig.** Implement an authorized removal by removing every key representing that member from the recognized multisig membership through an authorized contract transaction, migration or, where actually necessary, a blockchain System Upgrade. A routine authorized membership update does not require a blockchain software upgrade merely because it changes membership. Complete any separate corporate acts required for removal. Publish the legal effective date and the key-removal transaction; do not represent an unexecuted text vote as a completed key removal. Any lag between legal and technical effect must be disclosed and promptly resolved. The member targeted for removal need not approve the decision, but the transaction must satisfy the authorization rules actually in force or a separately approved lawful replacement mechanism. > > **2.4.5.4 Emergency Supervisor recommendations.** An Emergency Supervisor may investigate and recommend a removal within the approved remit. A recommendation alone does not authorize a discretionary removal or change of Board composition. Terra Governance retains the final decision, which may be given in the appointment proposal if it expressly identifies the person and action, or in a subsequent Binding Governance Decision. Implement an approved removal under Articles 1.11 and 2.4.4.1. This Article grants the Supervisor no additional unilateral removal power and does not restrict the operation of mandatory law or a binding court order. Append to §§2.2.5.1 and 2.4.5.2: > Voluntary-resignation notice periods do not create a discretionary grace period for a separately authorized removal or a resignation required under Article 4.6.2. Complete any legally required separation and key-removal steps promptly under Articles 1.11 and 2.4.4.1. Identify the legal effective date under the applicable instruments and the distinct technical removal date; an outstanding key does not excuse withholding the acts required for separation. Preserve any mandatory notice or contractual right until lawfully aligned; this bylaw alone does not amend an executed participation agreement. Append to §§2.2.6, 2.4.5.3 and 2.4.5.5: > Objectively established mandatory legal or contractual termination events remain subject to their valid procedures and accrued rights. A list of non-exclusive grounds supplies no independent discretionary removal power. An incumbent decision to invoke an at-will contract termination or disputed ground may not be used to evade the community approval required for discretionary director removal. Distinguish genuinely automatic events, contested facts and discretionary decisions and seek independent assessment of a dispute. Do not represent either a contract allegation or an investigative recommendation as a completed removal. Append to the Schedule 1 form of participation agreement, §8.1, and obtain the necessary corresponding amendments or other lawful alignment of executed agreements before relying on the changed rule: > The voluntary notice period does not apply to an involuntary termination lawfully authorized under the Bylaws or a resignation required under Article 4.6.2, subject to non-waivable law. Accrued rights and obligations survive as otherwise provided. A discretionary termination on behalf of the BORG that removes a serving Director shall follow the Bylaws' community-approval and valid implementation requirements. This addition takes effect for an executed agreement only through its applicable valid amendment or other lawful mechanism. **6. No temporary threshold authorization.** Proposal 2 does not insert or activate §3.2.1.8. Proposal 1 requires its own passage and lawful adoption. Its approval requirement and transition spending limits are not changed by this proposal. **7. Replace §3.2.5.2 and append to §3.2.5.3:** > **3.2.5.2 Terra Governance decisions.** Both ordinary and emergency Binding Governance Decisions under Article 1.11 shall be implemented through the relevant Mandatory Autonomous Systems and legally required corporate acts. No declaration of an Adverse Event or appointment of an Emergency Supervisor is a prerequisite to an ordinary Binding Governance Decision. Append: > For a transaction implementing a Binding Governance Decision, the Signature Decision concerns conformity with the passed decision, correct execution and Article 1.11.5. It does not reopen the merits. Intentionally withholding a signature as a policy veto is inconsistent with Article 1.11. Ordinary proposals that do not implement such a decision remain subject to independent substantive evaluation under this Article. **8. Add the following conforming provisions:** Append to §1.10: > The Veto Multisig retains its safeguards over decisions delegated to the Board. It shall not exercise an independent policy veto over faithful implementation of a specific Binding Governance Decision. A claimed implementation discrepancy shall follow Article 1.11.5. Existing technical vetoes, timelocks and approvals must be satisfied or lawfully changed; this provision does not itself bypass their code. An emergency designation does not suspend Terra Governance's final authority. Append to §3.2.5.4: > A Binding Governance Decision approving an expenditure or funding policy settles the policy choice only within its explicit amount or cap, permitted recipients or eligibility rules, purpose, duration and conditions. It does not authorize unspecified spending. Missing execution details must be published and resolved through a conforming implementation or a further express governance decision where the omission is material. Required Treasury transactions, accounting, solvency checks, token-holder approvals, timelocks and technical controls remain applicable until lawfully changed. No funding-policy label overrides conflict controls or a specific temporary spending restriction without an express approved change. Election deposits under proposal 4855 remain subject to its register, minimum-deposit, Treasury-approval and refund rules. This Article does not itself transfer funds or reopen that approved election policy. Insert §4.7: > **4.7 Express governance duties and conflicts.** Article 4's general limitations do not waive the express duties owed to the BORG under Article 1.11 or the existing Article 4.6.2. Maintain a public register of material financial relationships relevant to Foundation decisions, dated Board/community disclosures, the majority-of-disinterested-directors approvals for continued participation and any conditions. Update it within seven calendar days of becoming aware of a new material conflict or material change, and before an affected decision if earlier. This period does not postpone a duty to disclose, recuse or resign. Ordinary token ownership alone is not automatically a disqualifying conflict; material direct and indirect interests relevant to the decision must be assessed. Protected underlying records shall be available to an authorized independent reviewer with useful public summaries. Approval to continue serving is distinct from transaction approval. Public transfers or later disclosure do not establish historical compliance. Apply Article 4.6.2 according to its actual conditions, give affected persons an opportunity to supply records and respond, and publish the resulting action without automatically declaring past transactions unlawful or past payments recoverable. > > No beneficiary may approve their own project budget, milestone acceptance or payment release. New discretionary grants, fee increases, Treasury allocations or payment amendments benefiting a director or a business they own, control or materially benefit from require a public declaration, commercial justification and the applicable disinterested approvals. Existing enforceable obligations and essential services require documented, independently approved arrangements; that exception does not itself authorize new benefits or override a specific transition prohibition. Recusal does not reduce the applicable transaction minimum. If too few disinterested members can approve, disclose the impasse and use an independently authorized lawful remedy; no beneficiary may create an exception. This Article confers no temporary two-approval permission and does not authorize operation with fewer than three directors. Append to §5.2: > Authorized publication of the governance decisions, implementation status, reasons for delay and non-confidential acceptance evidence required by Article 1.11 is permitted. Protect private keys, protected personal data, legally privileged advice and information whose disclosure would breach an enforceable legal obligation. Provide a useful redacted summary where full publication is restricted. The Board may not classify the existence of a decision, its outcome or all reasons for non-implementation as confidential merely to prevent accountability. Add to Schedule 4's Terra Governance entry: > Final Foundation governance authority under Article 1.11, encompassing ordinary and emergency Binding Governance Decisions. Other Mandatory Autonomous Systems implement that authority subject to the legal and technical requirements expressly preserved in these Bylaws. **9. Conforming rules for invalid terms, prior commitments and oversight.** Replace §7.4 with: > **7.4 Severability.** An invalid or unenforceable provision shall not invalidate an independent remaining provision to the extent permitted by law. Comply with binding decisions of a competent court or tribunal and preserve its lawful powers. The Board may propose a replacement for an invalid provision but may not substantively replace or waive it without the express Terra Governance approval and lawful adoption required by Article 7.3. Pending a valid replacement, identify the affected act, preserve independent duties and pursue the lawful remedy under Article 1.11.5. Severability cannot be used to retain a new power while discarding the safeguards on which its approval depended; seek a further decision where that bargain cannot lawfully be implemented. Append to §7.5: > Adoption of this amendment package does not itself waive, release, retrospectively approve or determine the legal enforceability of an earlier published handover commitment or associated claim. Any asserted prior variation or release must be identified with its legal basis and adoption evidence. No general entire-agreement language in this package is approval of an otherwise unresolved departure. Append to §§2.5.3 and 2.5.5: > Appointment or removal of a standing Supervisor is subject to Article 1.11 when Terra Governance has expressly decided the matter, with all required constitutional, statutory and contractual steps completed. No reviewer or Supervisor receives additional technical signing authority by designation alone. A change to the reviewer or enforcement arrangement during an open review must follow the independence, replacement and funding conditions expressly approved for that engagement. Append to §2.6.2: > An independent financial or authority review does not itself constitute an Emergency Supervisor appointment or an Adverse Event declaration. Investigative findings do not themselves remove a director or adjudicate civil or criminal liability. Any remedy must follow its identified authority and competent process. **10. Adoption, prior decisions and verification.** Follow the post-passage adoption directions in the resolution. Preserve the full passed text and publish the dated implementation dossier, exact execution instruments, effective dates, notices, approvals and resulting governance documents. Later documents may implement only the policy actually approved; they are not retroactively incorporated into the vote. A valid adoption of this package does not retrospectively create a breach of a duty that did not yet exist. Carry forward the uncompleted directions in #4855 with its original specific timetable, nomination stages, candidate protections, deposit controls and appointment requirements. If Proposal 1 separately passes and is validly adopted, preserve its exact scope and clocks. Otherwise no obligation to remove its named director is imported. Completed work and paid review work are credited; overlapping obligations do not require duplicate payment, and the earlier applicable specific deadline is not restarted by the later adoption. A lawfully required shortfall in access or records is reported and pursued, not treated as completed work. Demonstrate correct operation at four and five members, after a recusal, with formal abstentions and with old proposal snapshots. No two-signature permission comes from this proposal. Publish gaps between bylaw duties and actual technical powers and the funded remedy. If multiple resignations or disqualifications would leave an unmanageable or inquorate Board, use an available lawful route or disclose the missing authority and seek specific further approval under Section 1. Do not invent a lower quorum or suspend a duty to resign. Do not implement a materially changed constitutional package under a generic instruction to counsel: seek express approval of the changed text. [bylaws]: https://raw.githubusercontent.com/phoenix-directive/docs/main/Phoenix%20Foundation%20-%20Bylaws.pdf [act]: https://legislation.gov.ky/cms/images/LEGISLATION/PRINCIPAL/2017/2017-0029/2017-0029_2025%20Revision.pdf These adopted restrictions govern authorized conduct; they do not by themselves establish that a transaction or agreement with a third party is void. The implementation dossier must distinguish legal duties, contractual terms and controls actually enforced by code. More details: https://gist.github.com/PFC-developer/9d3cebae67b5718b3a74699e40d921d9/f5c703162cb9b08a218dcec67aae6fe645d064dd#file-02-governance-and-accountability-md

Community

Up 0 Down 0 Comments 0

1XP X 0base.vc

Cosmos governance portal by 1XP Validator and 0base.vc

... chains Wallet ready