The Council of Fifty Conference: A Working Note

A working note on how the Council of Fifty conference runs, how its subcommittees form and work, and how its proposals become projects. It is keyed to the NewVistas Constitution, and describes a working arrangement wherever the constitution is silent. It accompanies The Council of Fifty and The Subcommittees of the Council of Fifty.

About this note

The constitution says what the Council of Fifty is and what it may never do (§12.9). It fixes the sequence every matter passes through (§3.12 and Chapter 9) and the community’s own quarterly conference (§6.5). It does not say how the Council of Fifty conference is organized, or how its proposals become projects on the ground. This note proposes a working arrangement for both. Where it goes beyond the constitution it says so, and if adopted, each community adopts it through its own bodies.

The quarterly cycle

Reporting at the end, planning at the start

Each quarter ends with the community’s own quarterly conference, on the Saturday and Sunday of week 13. The next quarter begins with the Council of Fifty conference in week 1. The first looks back; the second looks forward.

How the cycle runs

• Week 13, Sunday: each community reports, at home.
• Week 1: its bureau councils travel to the host community and plan together.
• Weeks 2 to 12: each community decides, at home, whether to adopt what was proposed.
• The next week 13, Sunday: each community reports what it decided, and the cycle begins again.

Getting a matter onto the agenda

It starts at home

A matter begins with one president, and only within the duty of his or her own office and bureau: the constitution asks every president to learn his duty and act in the office in which he is appointed (§5.1). It goes first to that president’s presidency of four, which confirms that it lies within its duty and office, asks whether the community can already settle it, and develops it into a well-prepared plan. The council of twelve then approves it by seven of twelve and develops it into a full plan, including how the work divides into parts, by default one for each community. Nothing skips a step (§3.12, Chapter 9).

Only shared matters go forward

A matter goes to the Council of Fifty only if it has passed both bodies and reaches beyond its own community. Anything a community can settle alone is settled at home. The community that raised it becomes the originating community, and the presidency that first supported it becomes the originating presidency.

Filing, withdrawing, and publishing the agenda

Matters may be filed until the end of week 12. The originating council of twelve may withdraw a matter at any time before the conference. The agenda is published to every delegation before the conference, so that every president can read it, and nothing can be added at the conference itself.

The Council of Fifty week

Why Tuesday to Thursday

The conference runs from Tuesday to Thursday of week 1. Monday is left for travel and setting up, and Friday stays free of meetings, as the constitution requires.

Keeping the meetings at home

Delegates hold their Monday presidency meetings at home before they travel. Every bureau council attends in full, so the regular 9:00 meetings that fall during the conference are held at the venue: the Segment councils of trustees and regulators on Tuesday, and bureau councils 1 to 12 on Thursday, which is the first Thursday of the quarter. No meeting at home is lost. The conference itself uses the community’s forty-five-minute blocks with fifteen-minute breaks, and the full timetable is set out below.

Venue and costs

The plenaries meet in the host community’s stadium, and the subcommittees in rooms near it. The host’s stadium, rooms, and guest suites are held by Business Enterprises, which charge their published fees. Each attendee pays his or her own travel, lodging, and share of those fees, so the host community carries no cost and the Council of Fifty needs no fund. No one is reimbursed, because no budget exists to reimburse anyone from.

The plenaries

Who presides

Both plenaries gather all 9,600 delegates. The host community’s presidency presides, its presidents taking turns to preside and keep the notes.

The opening plenary

The opening plenary is procedural. It confirms the agenda, publishes the membership of every subcommittee, and sets the order of presiding within each. It debates nothing of substance.

The closing plenary

The closing plenary receives each plan its subcommittee has approved, with the trustee and regulatory findings, and publishes it for every community to consider. It approves nothing on the communities’ behalf, and nothing it does binds any community.

The subcommittee

One subcommittee of twelve for each matter

Each matter is worked by one subcommittee of twelve, made up of three full presidencies of the same bureau: the presenting presidency, and one full presidency of each of the other two kinds, drawn at random from two different communities among the other forty-nine. Between them they bring the three duties of every bureau council: Operating, trustee, and regulatory. Every presidency holds one president from each Segment, so every subcommittee has three partnered men, three partnered women, three single men, and three single women.

How the presidencies are drawn

The two presidencies are drawn at random, never from volunteers, so that no special interest is present beyond the presenting presidency’s. The draw uses a public random number and a published procedure, selects offices rather than persons, and sets aside any presidency already drawn for another matter at the same conference. The full rules are set out in The Subcommittees of the Council of Fifty.

How it works

On Tuesday afternoon the subcommittee reads the originating community’s plan and agrees its order of presiding and note-keeping, the presenting presidency presiding in turns. Through Wednesday it examines and improves the plan; each evening the draft is posted to every delegation, and the bureau exchanges send comments for the next morning. Any delegate may sit in and speak, but only the twelve decide. On Thursday morning it decides by seven of twelve, and the trustee and regulatory presidencies each record a signed finding, which goes forward with the plan unchanged. A plan it does not approve returns home for further study.

After the conference

The subcommittee does not simply dissolve. Its twelve seats become the project’s review panel, which meets at each conference until the closing event, reviews each part’s progress, and publishes its findings; where it finds cause for concern, the owning council must publish a response by the next conference. The panel never governs. The originating presidency keeps the record and reports on the project at every conference until it is complete.

What everyone else is doing

Most delegates are not on a subcommittee

With thirty matters on the agenda, 360 presidents sit on subcommittees, leaving more than 9,000 delegates free. They take part in three ways, all of them in keeping with the constitution’s purpose for the Council of Fifty: to compare conditions, publish what is learned, and harmonize shared questions (§12.9).

Bureau exchanges

Each bureau’s delegates from all fifty communities meet together in a bureau exchange: the fifty communities’ Operating presidents for that bureau, with the trustees and regulators who serve it. The exchange compares conditions across the communities, shares what has worked, and notes questions that one of its members might later raise at home. Business figures are shared only as the competition protocol allows, late and in aggregate. Each exchange publishes a short note of what was learned at the end of the conference. Exchanges decide nothing and propose nothing; a question that should become a proposal must still begin with one president at home.

Reading and commenting on the drafts

Drafts are posted to every delegation each evening. Each bureau exchange reads the drafts in its own domain and sends its comments to the subcommittees concerned by the end of the afternoon, so every plan is improved by the wider field, not only by its twelve members.

Sitting in

Any delegate may sit in on any subcommittee and speak there, without a vote. Delegates may also visit the host community’s buildings and works, where its Business Enterprises offer tours at their published fees.

After the conference

Every other community decides for itself

The approved plan is published at the closing plenary. During weeks 2 to 12, the same bureau’s council in each of the other communities takes it up and decides, by seven of twelve, whether its community will take on its own part. That vote is the community’s own adoption, and each council first secures the support of its community’s other bureaus that would be involved. A community that declines remains in good standing, and its part is offered to communities that have adopted the plan, or the project is built in phases.

The Council of Fifty confirms, but never binds

At the next conference, the full Council of Fifty votes, by a majority of communities, on whether to carry the project forward as a Council of Fifty project, entered on its register and followed by its review panel. That vote decides only what the Council of Fifty itself does, and commits no community to anything.

Reporting back

On the Sunday of week 13, each stand seat reports what the Council of Fifty proposed in its bureau’s domain and what the community decided. At each conference until completion, the originating presidency reports on the project, and the review panel publishes its findings.

From proposal to project

No project above the communities

The Council of Fifty never owns, runs, or pays for a project, and the constitution allows no cooperatives. Each community that adopts a project owns its own part, by default one fiftieth of the road, mine, drill sites, pipeline, grazing land, farmland, or wilderness area, and the parts are joined by contracts between the businesses that run them. The constitution sets out this pattern for gas fields: each community owns its well sites, its equipment, and its section of the trunk line, each leased to a Business Enterprise that runs it and charges fees (§12.9).

What a proposal for shared works contains

• A common design and standards, so the parts fit together.
• A list of parts, each to be owned by one community, such as its wells, its section of line, or its injection site.
• Fee principles for using a part owned by another community.
• A participation condition, stating how many communities, or which parts, must be adopted before construction makes sense.
• A timeline keyed to the quarterly cycle.

Each part is originated at home

A community that adopts the design originates its own part in the ordinary way. Contractors submit business proposals; Bureaus 19, 20, and 21 test them for completeness, demand, and viability; title goes to the community’s own Trust; and the operating Business Enterprise leases the part.

When building starts

Each community adopts its part during weeks 2 to 12, and the full Council of Fifty confirms the project at the next conference. Each community’s part then starts once it passes that community’s own checks and its contractor begins.

When a part enters service

Each part is built by a consolidator on construction financing. At the closing event, once the part is built, tested, and producing the revenue its plan requires, the long-term financing closes, the lease activates, and the operating Business Enterprise takes custody (§4.15). A part that cannot prove its revenue does not finance or enter service.

Who pays

• Communities do not pay. A community has no budget: it holds title to everything, but it has no right to spend money. Communities that own no part of a project neither build it, operate it, nor fund it; their people use it and pay its fees.
• The owner borrows against the asset. Title is held by a title bureau, usually Bureau 2, which finances the work with a bank loan. The bank lends only once an operating business has agreed to lease the asset and shown that its fees will meet the payments.
• Revenue carries the cost. The finished asset must be worth more than its cost, and its income must cover the loan and leave a profit.
• Using another community’s section is paid for through published fees, charged by the business that runs it.
• Studies and prospecting are carried in the licensed contractors’ own plans and recovered through their fees.

Joining late, leaving, and disputes

• Joining late. A community that adopts the design later, or a new community, builds its own part and connects on the published terms. Where the project shares hinterland, the new community takes its share by the published formula on the day it is founded.
• Leaving. A community that withdraws keeps its part as its own; the contracts between operators govern what happens to the connections.
• When a part fails. If one community’s part does not reach service, no other community is liable for it.
• Disputes. Disputes between operators go first to arbitration, as all contract disputes in NewVistas do.

Timetables

The quarter at a glance

The conference week, hour by hour

Every session lasts forty-five minutes and is followed by a fifteen-minute break, except where a tea break follows instead. Lunch runs from 12:00 to 2:00. Tea is served at 10:45, at 3:45, and at 5:00 at the close of each day. The morning tea falls at 10:45 rather than 10:30 because the constitution fixes the first session at 9:00 to 9:45, so 10:30 would fall in the middle of a session.

A matter’s journey, start to finish

Safeguards for independence

• The conference plans and proposes; it never decides for any community.
• Every matter has passed its own community’s presidency of four and council of twelve before it is filed.
• Every president serves within the duty of his or her own office and bureau, and every subcommittee brings all three duties and every Segment, from three communities, drawn at random with no volunteering.
• Trustee and regulatory findings travel with every proposal and cannot be overruled.
• Presiding is a turn of duty, never a position, and no role carries over from one conference to the next.
• No body operates between conferences: review panels watch and publish, but never govern, and all work between conferences is done by the communities under the Council of Fifty’s auspices.
• Every proposal takes effect only where a community adopts it through its own bodies.
• Every part of every project is owned, financed, and paid for by one community, with no pooled fund or shared debt.
• The full Council of Fifty’s vote decides only what the Council itself does, and binds no community.