46. Meetings
46.1 Meetings On the Rail
46.1.1 Meetings within Planetary Nexus Governance are not the primary container of governance. They are governance interfaces operating on the Rail. Their purpose is to bring accountable human judgment, deliberation, synthesis, dissent, condition-setting, and authority into contact with already docketed matters, classified evidence, prepared decision packs, public authority capacity records, safeguards conditions, technical findings, and correction paths.
46.1.2 The Rail does not abolish meetings. It removes the illusion that meetings alone are governance. A meeting without intake, evidence, classification, authority record, participant capacity, decision record, output register, action ticket, and correction path is an institutional conversation, not a valid governance act. Meetings become legitimate when they sit within a records-first system that can show what was before the meeting, what happened during it, and what changed after it.
46.1.3 Meetings on the Rail may include Board meetings, General Assembly sessions, Helix Council sessions, Convergence Chamber sessions, Stewardship Committee meetings, TMD panels, National Council meetings, Leadership Council sessions, Investor Council sessions, public authority interface sessions, community-protected meetings, controlled-room reviews, routeability sessions, incident reviews, emergency sessions, and closeout meetings. Their forms may differ, but each must operate through the same core discipline: docket, capacity, evidence, deliberation, output, record, monitoring, correction.
46.1.4 A meeting on the Rail should never be convened merely because institutional habit requires gathering people. It should be convened because a matter requires human judgment, lawful decision, cross-role deliberation, public authority clarification, safeguards review, technical synthesis, routeability consideration, community engagement, dissent resolution, or correction. The meeting is justified by a governance need, not by calendar ritual.
46.1.5 Meetings must remain role-separated. A Board meeting does not become a TMD technical review. A Helix Council meeting does not become public authority approval. An Investor Council session does not become financial advice. A community meeting does not become consent unless the applicable consent process is satisfied. A technical panel does not become democratic legitimacy. The meeting record must preserve these limits.
46.1.6 Meetings must be supported by Nexus Platforms where appropriate, but platform attendance or digital workflow does not create authority. A platform meeting room supports governance by securing materials, recording capacity, preserving evidence, logging attendance, capturing decisions, issuing action tickets, and enabling correction. It does not supply the mandate.
46.1.7 The doctrine is direct:
Meetings on the Rail are human judgment interfaces within a larger governance infrastructure; they become valid only when connected to records, evidence, authority, capacity, outputs, monitoring, and correction.
46.2 Pre-Meeting Intake and Classification
46.2.1 Pre-meeting intake and classification are the steps that determine whether a matter is ready to be placed before a meeting, what type of meeting is appropriate, which actors should participate, what evidence is required, what authority is implicated, what safeguards apply, and what publication class governs the materials. No material matter should enter a governance meeting as an unstructured topic.
46.2.2 Pre-meeting intake should begin with a form or docketed submission identifying the matter, Case ID where applicable, submitting actor, actor capacity, requested meeting purpose, decision or deliberation sought, evidence available, public authority relevance, community implications, technical domain, data sensitivity, safeguards flags, routeability relevance, urgency, and correction history.
46.2.3 Classification should determine the meeting type. A matter may require Board decision, council deliberation, Helix review, TMD technical panel, safeguards review, public authority interface, controlled-room review, public-safe publication review, routeability session, community-protected engagement, incident meeting, emergency meeting, or closeout meeting. Convening the wrong meeting type can create authority confusion.
46.2.4 Pre-meeting classification must include publication class. Materials may be public, public-safe, controlled, restricted, security-sensitive, community-sensitive, protected knowledge, finance-sensitive, or public authority sensitive. Meeting invitations, materials, recordings, transcripts, notes, AI summaries, and outputs must follow the highest applicable protection level unless records are separated by access class.
46.2.5 Pre-meeting intake must include authority analysis. The convening function should identify whether the meeting is for information, deliberation, recommendation, decision, approval, ratification, correction, public-safe release, routeability, technical review, or handoff. Participants should know whether the meeting can decide anything and, if so, who has decision authority.
46.2.6 Pre-meeting intake must include safeguards review where people, communities, Indigenous or protected knowledge, vulnerable participants, public authority sensitivity, cyber risk, finance sensitivity, or public claims are implicated. A meeting may require protected channels, separate caucus spaces, confidentiality controls, non-retaliation measures, accessibility support, or public-safe mapping restrictions before it can proceed.
46.2.7 Pre-meeting classification must include readiness. A matter may be ready for discussion but not decision. It may be ready for technical review but not public release. It may be ready for routeability screening but not capital-reader review. It may be ready for public authority clarification but not public authority approval. The meeting should not be asked to do more than the docket supports.
46.2.8 The doctrine is direct:
Pre-meeting intake and classification ensure that meetings begin from governed matters, not vague topics, and that every convening is matched to the right purpose, authority, evidence, safeguards, and publication class.
46.3 Docket-Based Agendas
46.3.1 A docket-based agenda is an agenda built from Case IDs, decision questions, evidence states, authority paths, safeguards flags, technical review status, public authority capacity, routeability relevance, correction needs, and action requirements. It replaces agenda-setting by personality, politics, urgency theatre, or institutional habit with agenda-setting by governed matter status.
46.3.2 Docket-based agendas are necessary because traditional agendas often hide the real governance question. An item titled “AI infrastructure update” may actually require data-zone decision, public authority clarification, TMD review, community safeguards, energy-water baseline review, routeability restriction, or public claims correction. A docket-based agenda states the governance object clearly.
46.3.3 Each agenda item should identify the Case ID, matter title, meeting purpose, decision class, responsible function, time allocation, required materials, authority basis, participants needed, conflicts, dissent already recorded, evidence gaps, safeguards status, technical status, publication class, proposed output, and correction implications.
46.3.4 Docket-based agendas should distinguish information items, discussion items, deliberation items, recommendation items, decision items, ratification items, correction items, emergency items, and closeout items. A meeting should not treat all agenda items as equal. The record must show what kind of governance act is being requested.
46.3.5 Docket-based agendas should prevent late-stage surprise. New material matters should not be added without classification unless emergency or incident conditions justify it. Surprise decisions undermine record validity, participant capacity, and safeguards.
46.3.6 Docket-based agendas should expose dependencies. If an item cannot be decided until a TMD finding, public authority capacity record, safeguards review, legal review, or AEP update is completed, the agenda should state that dependency and avoid false decision pressure.
46.3.7 Docket-based agendas should include correction and closeout as standing governance categories. Meetings should not only create new work; they should correct old work and close completed matters. A Rail that only adds agenda items and never closes or corrects them becomes bureaucratic accumulation.
46.3.8 The doctrine is direct:
Docket-based agendas make meetings accountable to the Rail by requiring every agenda item to identify its matter, purpose, authority, evidence state, safeguards status, decision need, and expected record consequence.
46.4 Evidence Packs and Decision Packs
46.4.1 Evidence Packs and Decision Packs are the primary materials through which meetings become decision-capable. An Evidence Pack provides the structured evidence object, including lineage, provenance, uncertainty, quality levels, gaps, rejected evidence, safeguards conditions, technical review, and correction history. A Decision Pack converts that evidence into the specific question, options, authority, risks, conditions, and proposed record action before the meeting.
46.4.2 Meetings should not be asked to make material decisions from slide decks, verbal briefings, promotional narratives, informal summaries, or AI-generated notes alone. Such materials may support comprehension, but they cannot replace AEPs, Baselines, TMD findings, safeguards records, public authority capacity records, publication records, or other governed evidence objects where those are required.
46.4.3 A meeting Evidence Pack should identify what the meeting may rely on and what it may not rely on. It should show evidence quality, source restrictions, uncertainty, contested points, evidence gaps, community concerns, public authority limitations, technical limitations, and correction history. The purpose is not to persuade the meeting toward a predetermined outcome; it is to enable accountable judgment.
46.4.4 A Decision Pack should identify the decision question, competent authority, procedure, quorum or threshold where relevant, options, recommended action if any, conditions, required recusals, public claims impact, public authority implications, safeguards implications, technical implications, routeability implications, downstream effects, and correction path.
46.4.5 Decision Packs must be role-specific. A Board Decision Pack differs from a TMD panel pack, a Helix Council pack, a Leadership Council maturity pack, an Investor Council routeability pack, a public authority interface pack, and a community-protected meeting pack. The same evidence may be framed differently for different lawful roles, but the underlying record must remain consistent.
46.4.6 Decision Packs must show non-effect. If the meeting can recommend but not decide, the pack must state that. If the meeting can decide public-safe release but not execution, the pack must state that. If the meeting can confirm routeability for controlled review but not financial suitability, the pack must state that. The meeting must know its limits.
46.4.7 Evidence Packs and Decision Packs must be updated after the meeting. If deliberation changes conditions, adds dissent, requests correction, defers decision, or modifies scope, the packs should be marked, versioned, and linked to the meeting record. The materials should not remain frozen as though the meeting did not occur.
46.4.8 The doctrine is direct:
Evidence Packs give meetings trustworthy substance; Decision Packs give meetings lawful questions. Together, they turn human deliberation into informed, bounded, record-valid governance.
46.5 Capacity Records for Participants
46.5.1 Capacity Records for participants identify who is present in a meeting, what role they hold, what authority they have, what authority they do not have, whom they may represent, whether they may vote or decide, whether they are observing, whether they are contributing expertise, whether they are speaking personally or institutionally, and what restrictions apply to their participation.
46.5.2 Capacity Records are essential because meetings are highly vulnerable to role confusion. A public official may be present as observer but be described later as approving. A community participant may share evidence but be described as consenting. A technical expert may advise but be described as certifying. A finance actor may provide diligence questions but be described as endorsing. A sponsor may attend but be treated as a governance actor. Capacity Records prevent these conversions.
46.5.3 Participant capacity should be recorded before the meeting and confirmed at the start where material. The record should identify participant name or protected class, organization, role, capacity, authority, voting status, speaking capacity, conflict status, confidentiality obligations, publication permission, public claims permission, and any recusal or access limit.
46.5.4 Public authority capacity must be especially precise. The record should state whether the public actor participates as observer, data provider, technical contributor, policy body, regulator, public finance actor, procurement authority, emergency authority, host, lawful decision-maker, or other specific capacity. If public reference is not permitted, the record must say so.
46.5.5 Community and Indigenous capacity must be especially protected. A participant may speak as an individual, local organization, affected person, knowledge holder, youth representative, elder, community observer, governance representative, consent authority where applicable, or protected participant. No meeting record should generalize one participant’s capacity into community-wide consent or support.
46.5.6 Capacity Records must also include machine and platform roles where relevant. If AI assists meeting summaries, if a platform administrator attends, if an agentic workflow prepares notes, or if digital tools process materials, the record should state the machine or technical role and limitations. Invisible machine assistance can affect meeting meaning.
46.5.7 Capacity Records must travel into the minutes, outputs, public-safe summaries, decision registers, and publication records. Public-facing outputs must not say more about participants than the capacity record permits.
46.5.8 The doctrine is direct:
Capacity Records ensure that every meeting participant is understood in the role they actually hold, so attendance never becomes authority, expertise never becomes certification, and participation never becomes consent.
46.6 Deliberation, Dissent, and Conditions
46.6.1 Deliberation is the human judgment process through which participants examine evidence, test assumptions, identify public value, surface uncertainty, apply safeguards, clarify authority, hear affected voices, evaluate options, and shape conditions before a decision or output. It is one of the core reasons meetings remain necessary within the Rail.
46.6.2 Deliberation must be evidence-aware but not evidence-blind. Evidence provides the structured basis for discussion, but human judgment must ask whether evidence is complete, whether it misses lived experience, whether technical conclusions are overstated, whether ecological constraints are respected, whether public authority capacity is clear, whether community safeguards are adequate, and whether the record is ready for reliance.
46.6.3 Dissent must be invited, protected, and recorded. A meeting that pressures participants toward consensus without preserving material dissent produces false legitimacy. Dissent may include technical disagreement, community objection, public authority limitation, safeguards concern, legal concern, finance-readiness concern, ecological concern, uncertainty, or refusal. Dissent is not disruption; it is governance intelligence.
46.6.4 Conditions must be recorded with precision. A meeting may approve only if a TMD review is completed, a public authority capacity record is clarified, a public-safe summary is revised, protected knowledge is removed, a proof pack is limited, a dashboard label is changed, a community grievance route is opened, or a Baseline is updated. Conditions must become action tickets, not meeting memory.
46.6.5 Consensus-first deliberation must not erase dissent. Consensus is valuable when it reflects genuine convergence. It is invalid when produced by exhaustion, hierarchy, intimidation, language barriers, technical opacity, lack of evidence, time pressure, or fear of retaliation. The Rail should distinguish consensus, no objection, unresolved dissent, conditional support, abstention, and refusal.
46.6.6 Voting, where required or appropriate, must follow the applicable rule. The meeting record should state voting eligibility, quorum, threshold, votes, abstentions, recusals, dissent, and conditions. A vote cannot cure missing authority, defective notice, unmanaged conflict, or unresolved legal requirement.
46.6.7 Deliberation should identify re-scoping. If the meeting finds that the proposed claim, decision, release, maturity, routeability, or handoff is too broad, the proper output may be narrowed scope rather than approval or rejection. Re-scoping is often the mature outcome of deliberation.
46.6.8 The doctrine is direct:
Deliberation gives the Rail human judgment; dissent gives it honesty; conditions give it discipline. Meetings are legitimate when they preserve all three in records capable of action and correction.
46.7 Meeting Outputs as Records
46.7.1 Meeting outputs must become records. A meeting may produce decisions, recommendations, findings, conditions, dissent records, action tickets, referrals, holds, corrections, public-safe publication approvals, TMD questions, routeability directions, public authority capacity clarifications, safeguards escalations, closeout actions, or no-decision records. Each output must be recorded according to its governance effect.
46.7.2 Meeting minutes are not enough if they merely summarize discussion. A meeting output record should identify what was decided or not decided, who had authority, what evidence was relied on, what conditions were imposed, what dissent was recorded, what conflicts were managed, what action tickets were created, what records must be updated, what public claims are permitted, and what correction path applies.
46.7.3 Meeting outputs should distinguish record types. A recommendation is not a decision. A decision is not execution. A condition is not completion. A referral is not approval. A public-safe release approval is not public authority approval. A routeability direction is not investment advice. The output record must name the type.
46.7.4 Meeting outputs must be linked to Case IDs and dockets. If a meeting output cannot be linked to a docket, the Rail cannot track follow-through or correction. Each material output should update the relevant Case ID, Decision Register, action ticket list, publication record, TMD queue, safeguards register, routeability record, or correction trail.
46.7.5 Meeting outputs must capture non-decisions. A meeting may defer, hold, decline, re-scope, request evidence, require public authority clarification, or determine that it lacks authority. These are governance outputs. They must be recorded so silence is not mistaken for approval.
46.7.6 Meeting outputs must control public meaning. If the meeting produces an external communication, public-safe summary, registry update, dashboard state, proof-pack revision, or public authority reference, the output must include claims limits. Participants should not separately describe the meeting beyond permitted claims.
46.7.7 Meeting outputs must have owners and timelines. Each condition or action should identify responsible function, due date or review window, required receipt, escalation path, and closeout condition. Outputs without owners are not governance; they are aspirations.
46.7.8 The doctrine is direct:
Meeting outputs become governance only when converted into precise records that state the output type, authority, evidence basis, conditions, dissent, responsible actors, claims limits, and correction path.
46.8 Post-Meeting Monitoring and Correction
46.8.1 Post-meeting monitoring and correction are the processes that ensure meeting outputs are implemented, tracked, reviewed, corrected, and closed. A meeting is not complete when participants leave or the platform room closes. It is complete only when its outputs have entered the Rail and their consequences are monitored.
46.8.2 Post-meeting monitoring should confirm that decision registers are updated, action tickets issued, publication records revised, public-safe outputs prepared, dashboards updated, role keys changed, TMD referrals routed, safeguards holds applied, routeability records corrected, public authority capacity records clarified, and closeout conditions tracked.
46.8.3 Post-meeting monitoring must identify contradictions between the meeting output and the record. If the meeting approved a condition but the dashboard shows unconditional status, correction is required. If minutes imply consensus but dissent was recorded, correction is required. If public claims exceed the output, correction is required. If a participant’s capacity was misstated, correction is required.
46.8.4 Post-meeting correction must be possible for participants. A participant should be able to challenge minutes, capacity description, dissent record, public-safe summary, decision wording, or claims attribution where the record misrepresents the meeting. This is especially important for public authorities, communities, protected participants, and technical experts.
46.8.5 Post-meeting monitoring must include action aging. Action tickets that remain unresolved should escalate according to urgency and consequence. A meeting that creates actions without follow-through becomes institutional theatre.
46.8.6 Post-meeting correction must include public-safe correction where reliance occurred. If an inaccurate meeting output was published, quoted, displayed, or used downstream, correction must travel through the same relevant channels.
46.8.7 Post-meeting learning should identify whether the meeting was necessary, properly prepared, correctly constituted, evidence-ready, inclusive, secure, and effective. Repeated poor meeting outcomes may indicate problems in intake, docketing, platform design, authority records, or culture.
46.8.8 The doctrine is direct:
Post-meeting monitoring and correction ensure that meetings remain connected to action, public meaning, and accountability after deliberation ends.
46.9 Hybrid, Digital, Controlled, and Protected Meetings
46.9.1 Hybrid, digital, controlled, and protected meetings are meeting formats designed to allow secure, accessible, role-keyed, geographically distributed, confidentiality-aware, community-protective, and technically supported governance. They reflect the reality that planetary governance cannot depend only on physical rooms.
46.9.2 Digital meetings may occur through Nexus Platforms, secure portals, controlled rooms, clean rooms, encrypted channels, or other approved environments. They should support identity, capacity records, role-keyed access, agenda control, evidence review, voting or consensus where applicable, dissent capture, recording controls, AI-use controls, audit logs, and correction.
46.9.3 Hybrid meetings must avoid two-tier participation. Remote participants should not become second-class participants. Community participants, disabled participants, rural participants, low-bandwidth participants, and protected participants should be able to participate meaningfully. Accessibility is governance validity, not convenience.
46.9.4 Controlled meetings are meetings where records, evidence, public authority materials, technical findings, finance-sensitive materials, cyber-sensitive materials, legal materials, or restricted data require controlled access. Controlled meetings must define who may attend, what may be viewed, what may be exported, whether AI may be used, whether notes may be taken, and how outputs are classified.
46.9.5 Protected meetings are meetings designed for vulnerable participants, communities, Indigenous or local knowledge holders where applicable, whistleblowers, workers, or affected persons who require safeguards. Protected meetings may require confidentiality, separate spaces, trusted facilitators, local language, non-retaliation, no recording, protected note-taking, limited attendance, and careful public-safe outputs.
46.9.6 AI-assisted meeting tools must be controlled. Automated transcription, summarization, translation, action extraction, sentiment analysis, or meeting agents must not process restricted, protected, public authority-sensitive, community-sensitive, or finance-sensitive materials unless authorized. Machine-generated minutes require human review.
46.9.7 Meeting format must match matter risk. A high-risk public authority-sensitive or protected knowledge matter should not be handled in ordinary video conferencing. A low-risk public education session may be public. A finance-sensitive routeability session may require controlled access. Format is part of governance design.
46.9.8 The doctrine is direct:
Hybrid, digital, controlled, and protected meetings allow the Rail to convene across distance and sensitivity, provided that access, identity, confidentiality, AI use, accessibility, safeguards, and records are governed by design.
46.10 Meetings as Human Judgment Moments
46.10.1 Meetings remain essential because some governance acts require human judgment in real time. Evidence can be structured, AI can summarize, platforms can route, dashboards can display, and forms can classify, but human beings must still interpret meaning, weigh values, hear affected voices, resolve uncertainty, assume accountability, and decide within lawful roles.
46.10.2 A meeting is a human judgment moment when the matter requires deliberation among roles: Board fiduciary judgment, member constitutional judgment, Helix legitimacy judgment, public authority clarification, TMD expert judgment, safeguards judgment, community-protected dialogue, routeability judgment, or emergency judgment. The Rail prepares the meeting so judgment can be better, not eliminated.
46.10.3 Human judgment is necessary where evidence is incomplete, legitimacy forms conflict, public authority boundaries are unclear, community concerns are contested, technical uncertainty remains, ecological constraints are severe, finance-readiness risks capture, public-safe communication requires care, or correction requires institutional accountability.
46.10.4 Human judgment must be accountable. Meeting participants should not hide behind the platform, AI summaries, consultants, technical experts, or prior records. If they decide, recommend, condition, defer, or correct, the record should show their role and authority.
46.10.5 Human judgment must be humility-based. The purpose of a meeting is not to perform confidence. It is to understand the record, test assumptions, preserve dissent, ask what is missing, protect affected people, and decide only what the meeting is competent to decide.
46.10.6 Human judgment must be supported by machine assistance without being replaced by it. AI may help retrieve evidence, summarize materials, identify contradictions, draft action tickets, and monitor dependencies. But it cannot hear moral weight, hold public responsibility, grant consent, assume fiduciary duty, or exercise public authority.
46.10.7 Human judgment must remain open to nature and place. Natural-system signals, ecological baselines, field truth, and community evidence must be allowed to challenge institutional assumptions. Meetings should not become rooms where humans discuss abstractions detached from the living systems and people at stake.
46.10.8 The doctrine is direct:
Meetings are human judgment moments within the Rail: places where prepared evidence meets accountability, values, dissent, authority, safeguards, and the responsibility to decide or refrain from deciding.
46.11 Meeting Legitimacy Tests
46.11.1 Meeting Legitimacy Tests are the criteria used to determine whether a meeting was properly convened, properly constituted, properly informed, properly recorded, and capable of producing valid governance outputs. They prevent meetings from becoming legitimacy theatre.
46.11.2 The first test is purpose. Did the meeting have a defined governance purpose, Case ID, agenda, decision question, review question, correction question, or deliberation need? A meeting without purpose is not a valid governance interface.
46.11.3 The second test is authority. Was the meeting convened by a competent function? Did the participants know whether the meeting could decide, recommend, deliberate, review, correct, or only receive information? Were voting or consensus rules clear where applicable?
46.11.4 The third test is evidence. Were Evidence Packs, Decision Packs, Baselines, TMD findings, safeguards records, public authority capacity records, or other required materials available in time and in the proper publication class? Did participants know what was uncertain, missing, contested, or restricted?
46.11.5 The fourth test is capacity. Were participant roles recorded accurately? Were public authorities, communities, experts, finance actors, sponsors, hosts, providers, and platform administrators classified correctly? Were conflicts and recusals managed?
46.11.6 The fifth test is safeguards. Were vulnerable participants protected? Were accessibility, language, cultural protocol, protected knowledge, non-retaliation, confidentiality, and public-safe mapping concerns addressed? Were community claims prevented from overstatement?
46.11.7 The sixth test is deliberation. Was dissent invited and recorded? Were conditions captured? Was uncertainty preserved? Was consensus genuine rather than coerced or assumed?
46.11.8 The seventh test is output. Did the meeting produce appropriate records: decision register entries, recommendations, action tickets, dissent records, correction records, referrals, holds, closeout records, or no-decision records? Were public claims limits stated?
46.11.9 The eighth test is follow-through. Were outputs implemented, monitored, corrected, and closed? Did the meeting create record consequence rather than institutional memory?
46.11.10 The doctrine is direct:
A meeting is legitimate only when its purpose, authority, evidence, capacity, safeguards, deliberation, outputs, and follow-through can be shown in the record.
46.12 No Meeting Without Record Consequence
46.12.1 The final doctrine of this chapter is no meeting without record consequence. A meeting within Planetary Nexus Governance should either create, update, clarify, condition, defer, correct, refer, close, or validate records—or it should not be convened as a governance meeting. Conversation may be useful, but governance requires record consequence.
46.12.2 Record consequence does not always mean decision. A meeting may produce a dissent record, evidence-gap register, public authority capacity clarification, safeguards hold, TMD question, routeability limitation, re-scoping note, public-safe publication condition, action ticket, closeout record, or determination that no action is yet valid. These are all record consequences.
46.12.3 Meetings without record consequence create institutional risk. They allow participants to believe something was agreed when nothing was recorded. They allow actors to claim support without basis. They allow public authorities to be misrepresented. They allow community participation to be overstated. They allow technical issues to remain unresolved. They allow action items to disappear. They allow correction to fail.
46.12.4 No meeting without record consequence also protects participants. Participants should know what will happen with their contribution, whether their dissent is recorded, whether their capacity is protected, whether their evidence enters a docket, whether public claims may be made, and how they may correct the record.
46.12.5 This doctrine makes meetings more valuable, not less. When meetings have record consequence, participants prepare better, evidence is clearer, decisions are more precise, dissent is safer, outputs are actionable, and correction is possible. Meetings become fewer, deeper, more legitimate, and more useful.
46.12.6 The Rail should therefore treat meetings as one of several governance interfaces: alongside forms, dockets, evidence packs, platforms, controlled rooms, observatories, TMD reviews, public-safe dashboards, proof packs, correction trails, and handoff records. Meetings matter because they add human judgment to this infrastructure, not because they replace it.
46.12.7 A meeting that produces no record may still be an informal discussion, learning session, relationship-building moment, or exploratory conversation. But it should not be cited as governance authority, public approval, community consent, technical verification, routeability, maturity, recognition, or institutional decision.
46.12.8 The final doctrine is direct:
In Planetary Nexus Governance, meetings are not abolished; they are disciplined. No meeting becomes governance unless it leaves a valid record consequence that the Rail can monitor, correct, and learn from.
Last updated
Was this helpful?