# Claims ## Claim 1 — A company can be designed around completion rather than organizational growth **status:** speculative **what is real:** The candidate architecture explicitly separates business success from mandatory headcount/branch growth. **what is inference:** Some real firms can remain durable at two core livelihoods while demand is served by additional independent nodes. **what is missing:** multi-year operating evidence. **article rule:** Present as the central hypothesis, not a result. --- ## Claim 2 — The two-person rule means two core livelihoods, not literally only two humans **status:** strong as internal definition **what is real:** Supplementary paid shifts are allowed and tracked. **what is inference:** This can preserve a small operator core without hiding structural labour. **what is missing:** a healthy support-labour threshold. **article rule:** Never describe unpaid or invisible labour as proof of a two-person company. --- ## Claim 3 — Demand is information, not an order to scale **status:** design principle **what is real:** A node can respond to excess demand through scarcity, pricing, productivity, reduced availability or voluntary replication elsewhere. **what is inference:** This can preserve operator control without preventing market expansion. **what is missing:** customer tolerance and real competitive behavior. **article rule:** Do not treat sold-out states as automatically good. --- ## Claim 4 — Display variety and production variety are different variables **status:** strong as design distinction **what is real:** A market surface can display more variants than one node produces in one cycle through inventory and exchange. **what is inference:** Specialization may reduce local production complexity while preserving customer choice. **what is missing:** real inventory and exchange costs. **article rule:** Keep D (displayed variety) separate from P (produced variety). --- ## Claim 5 — Specialization can occur without compulsory concentration **status:** medium as architecture; speculative economically **what is real:** Independent nodes can hold different capabilities and trade batch outputs. **what is inference:** A network can gain specialization without requiring one central owner. **what is missing:** real counterparty economics and resilience. **article rule:** Measure dependency; do not call a network decentralized merely because legal entities differ. --- ## Claim 6 — The market can be geographically larger than the company **status:** speculative **what is real:** Products and customers can move beyond a node's immediate locality. **what is inference:** A small producer may reach a regional market without opening branches. **what is missing:** real catchment, logistics and repeat demand. **article rule:** Present as a hypothesis. --- ## Claim 7 — Community demand can reduce entry uncertainty without controlling daily production **status:** speculative but coherent **what is real:** The design separates durable category commitment from product-level pre-orders and separates stewardship from recipes/pricing/workflow. **what is inference:** This can reduce launch risk without turning operators into employees of a committee. **what is missing:** real community adoption and legal wrapper. **article rule:** No claim that membership or prepaid credit guarantees viability. --- ## Claim 8 — Operator autonomy, local stewardship and network interoperability are separate governance layers **status:** strong as architecture **what is real:** The pack defines different decision domains. **what is inference:** The separation can avoid both franchise control and community micromanagement. **what is missing:** legal implementation and conflict cases. **article rule:** Preserve the anti-franchise and anti-committee tests. --- ## Claim 9 — Node identity can outlive one legal company or operator generation **status:** candidate protocol rule **what is real:** The pack separates node lineage from legal ownership. **what is inference:** This can preserve local history while allowing fair operator exit and qualified succession. **what is missing:** legal enforceability. **article rule:** Do not imply a network credential can override property law. --- ## Claim 10 — A thin network layer should charge for service burden, not automatically for node success **status:** candidate financing rule **what is real:** Registry, lineage, map and credential costs need not rise in proportion to a node's sales. **what is inference:** A fixed transparent fee may reduce franchise-style extraction. **what is missing:** real network operating costs. **article rule:** No fee amount is validated. --- ## Claim 11 — Verification should attach to claims and risk, not a permanent global badge **status:** candidate protocol rule **what is real:** Different claims carry different consequences and evidence burdens. **what is inference:** Risk-proportional verification can preserve trust with less bureaucracy. **what is missing:** field-tested audit rules. **article rule:** Record-valid is not the same as externally checked. --- ## Claim 12 — Verification power needs appeal **status:** strong governance principle **what is real:** A network that can suspend claims/capabilities exercises power. **what is inference:** Independent appeal and time-bounded review reduce arbitrary control. **what is missing:** real reviewer and appeal institutions. **article rule:** Complaint triggers attention; evidence drives outcome. --- ## Claim 13 — The network itself can become the centralization failure **status:** strong failure-mode claim **what is real:** Shared registries, credentials and support create a central layer. **what is inference:** Measuring support, verification and adverse-action load can reveal drift toward headquarters. **what is missing:** live network data. **article rule:** Preserve the red line: the network should not become the largest company in the network. --- ## Claim 14 — The core architecture passes an internal coherence test **status:** medium as internal consistency only **what is real:** Gate 26 walks one node from formation through succession without an obvious contradiction between current design rules. **what is inference:** The model merits applied testing. **what is missing:** commercial, legal and operational validation. **article rule:** Never call this a viability pass.