Viable System Model

PXS promises no price. The design notes argue that it is nonetheless a coherent system, and they make the argument with Stafford Beer's Viable System Model: a description of the functions any system needs in order to keep its identity in a changing environment. This page summarises the model, sets the design's mapping against the running chain, and says where the correspondence is exact and where it is still a metaphor.

The model in brief

Stafford Beer, in Brain of the Firm (1972) and The Heart of Enterprise (1979), argued that every viable system, from a cell to a company, performs five functions:

Two more ideas complete it:

• Recursion. Every viable system contains viable systems and is contained in one.
• Algedonic signals. Pain or pleasure signals that bypass the normal channels when something goes badly wrong, so the whole system hears at once.

The model rests on Ashby's law of requisite variety: a regulator must be able to respond in as many ways as the disturbances it faces (Variety and Regulation).

The design's mapping, set against the chain

System by system

1 · Operations: the Atlas

The chain counts the Atlas exactly: P, all PIXA, liquid and staked. What it does not yet contain is the economy the design describes. On 2026-10-06 about 67.5% of all PIXA was stake still held by the two allocation accounts (The Four Components), and the marketplace for artworks is planned for 2027 (Roadmap). The operations exist; their weight is still mostly an allocation waiting to be distributed.

2 · Coordination

Several rules damp oscillation, each at the price of a slower response:

• Stake leaves in 13 weekly instalments, so a voter stays exposed to the result of its vote for months (Pixa Power).
• New stake waits 30 days before it counts in governance (Decentralization and Safeguards). The design notes do not name this rule, but it does System 2's work.
• The feed passes through two medians, across witnesses and over 84 hours (Oracle and Price Feed).
• Conversions wait 3.5 days, and settle at the median at the end (Haircut, Corridor and Settlement).

3 · Control, and its audit

Control has two instruments on chain, where the design names one:

• A gate. At a debt ratio of 20%, PXS printing stops: author rewards stop creating PXS and new conversions into PXS are refused. The fund's share of issuance and proposal pay continue.
• A rate. Above 30%, the haircut lowers what each PXS converts into.

Both thresholds are on Chain Parameters.

The audit channel, 3*, is public. The chain recomputes the debt ratio in every block, after updating the median (database.cpp:2349-2361), and anyone can read the inputs with condenser_api.get_dynamic_global_properties, condenser_api.get_feed_history and, for the treasury's balance, condenser_api.get_accounts.

4 · Intelligence: the Oracle

System 4 looks outward and ahead. On chain, it looks outward through the witnesses' feeds. Until mid-October it saw a constant: every feed divided by the same placeholder, so the system had no reading of PIXA's market. Since then most feeds read PIXA's one market and the Big Mac of their witness's country, so the channel carries a signal. The median, which is what the regulator acts on, still rested on placeholder values on 2026-11-03 (what it reads today). Nothing on chain looks ahead. Anticipation happens off chain, in people: witnesses who change their software, and developers who propose hardforks.

5 · Policy

The design gives policy to "binding witness consensus" and names the identity it holds: PXS measures an ideal of purchasing power, not a fiat number. The chain holds less than that:

• The identity is not encoded. The code calls the unit HBD internally, and accepts any price a witness publishes. That the price refers to a Big Mac is a convention of the feed software and of this documentation.
• Changes need the witnesses. A rule changes only by hardfork, approved by a supermajority of the scheduled witnesses (Protocol Upgrades).
• The witnesses answer to few voters. On 2026-10-05, six accounts, five of them with stake, had elected all nine. On 2026-11-03, 23 accounts had cast every witness vote, for 21 scheduled witnesses (database_api.list_witness_votes; Decentralization and Safeguards).

In Beer's terms, System 5 exists, but it is narrow, and it rests on practice rather than on rules.

The algedonic alert

When the haircut applies, the chain records a system_warning virtual operation every hour, reading in Hive's words "HIVE price corrected upward due to 30% HBD cutoff rule" (database.cpp:2517-2524). A PIXA → PXS conversion whose collateral falls short records another (Haircut, Corridor and Settlement). Any node, app or person watching the chain receives both at once. The print stop raises no such signal: it changes one field, pxs_print_rate.

Recursion

PXS's four parts sit inside the Pixa network, which can be read as a viable system of its own:

• Operations: publishing, curating and producing blocks.
• Coordination: the witness schedule and the medians.
• Control: the reward rules and the Decentralized Pixa Fund.
• Intelligence: the witnesses, and the developers who propose changes.
• Policy: the stakeholders and, off chain, the three entities that develop, steward and operate the project (Who Does What).

The network in turn sits inside larger systems: the markets PIXA may trade on, the jurisdictions its entities answer to, and the Hive codebase it follows.

What the mapping shows, and what it cannot

It shows what each mechanism is for. The haircut is a control function, not a guarantee. The medians are coordination. The feed is a sensor, and today a sensor that reads nothing.

It locates the gaps. Intelligence has no signal yet, policy rests on few hands, and the base is mostly undistributed.

It cannot prove viability. Beer's model lists the functions a viable system needs; having them does not make a system survive. A mapping like this one can be drawn for almost any organisation. Its value lies in the gaps it reveals, not in the fit it claims.

Inherited → changed

Sources

• Stafford Beer, Brain of the Firm (Allen Lane, 1972; second edition, Wiley, 1981) and The Heart of Enterprise (Wiley, 1979).
• W. Ross Ashby, An Introduction to Cybernetics (Chapman & Hall, 1956).
• PXS design notes (Pixagram, June 2026), §3.2, §5.1 and the glossary.
• Code, at commit 48f75a2: the order of the per-block updates, database.cpp:2349-2361; the warning, 2517-2524.