Run any Skill in Manus with one click

python-state-failure

Stars0

Forks0

UpdatedJuly 15, 2026 at 03:34

Fires when live state or a transport client is about to land somewhere wrong instead of the matching construct in python-state-success — frozen=True on the consistency model, a client field with no verb emitting through it, or arbitrary_types_allowed=True on any model other than the consistency model.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kyzodb

kyzodb/kyzo-python

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	python-state-failure
description	Fires when live state or a transport client is about to land somewhere wrong instead of the matching construct in python-state-success — frozen=True on the consistency model, a client field with no verb emitting through it, or arbitrary_types_allowed=True on any model other than the consistency model.

State — failure patterns

Three ways live state or a transport client escapes the one node allowed to hold it (the consistency model, python-state-success).

Frozen live edge

Freezing the consistency model contradicts what it is: the one node holding live clients and accumulating mutable state. Frozen, it is a different construct wearing the name.

The consistency model is the single unfrozen BaseModel of a context, with arbitrary_types_allowed=True, clients as fields, and state evolution by re-pointing a field to a newly constructed proven fact. A frozen domain composite holding no client is a concept model, not this.

class MarketSession(BaseModel, frozen=True):   # the consistency model is unfrozen; drop frozen=True and add arbitrary_types_allowed=True
    book: CoinbaseBook

Dead handle

A client held on the consistency model but reached by no verb is a capability wired to nothing: structure with no act crossing through it.

Every client field exists for a verb that crosses through it. A verb is a state transition on the consistency model that may emit the constructed fact through a client field; a client no verb touches names no transition and belongs nowhere, or its verb is missing and must be modeled.

class MarketSession(BaseModel):
    coinbase: CoinbaseClient   # no verb ever touches self.coinbase: either a verb must emit through it, or the field is unwired structure

Arbitrary type off the edge

arbitrary_types_allowed anywhere but the one live model lets an unmodeled foreign object sit inside a value: meaning the ontology never described.

arbitrary_types_allowed is legal on the consistency model and nowhere else, because that is the one node where live clients converge. A foreign system's data shape entering a frozen value is a foreign model (python-adapters-success), named for the foreign thing, lifting whole; a live client is held only by the consistency model.

class Snapshot(BaseModel):
    model_config = ConfigDict(arbitrary_types_allowed=True)   # legal only on the consistency model
    client: SomeSDKThing   # a live client belongs on the consistency model; foreign data belongs in a foreign model

More from this repository

same repository

python-adapters-failure

kyzodb/kyzo-python

Fires when a boundary crossing is about to be hand-rolled instead of built as the matching construct in python-adapters-success — a before-validator that indexes/renames/routes/computes on raw foreign data, a try/except catching Exception or ValidationError or running multiple statements in its except body, or .model_dump/.model_dump_json called anywhere but a route reply or client binding.

2026-07-150

python-adapters-success

kyzodb/kyzo-python

Build the three boundary-crossing constructs — foreign model, contract model, ordered union — the only shapes for data crossing in or out of the program. Fires before touching a foreign payload, file format, message, or client reply; before declaring an API surface or response shape; or before writing a try/except, error handler, retry, fallback, or None-check around foreign input.

2026-07-150

python-state-success

kyzodb/kyzo-python

Build the two live-node constructs — consistency model and binding — the only places mutable state and transport clients are allowed to converge. Fires before holding a socket, database, bus, or client; before declaring a mutable field; before writing a manager, an engine, or a second unfrozen model in a context; or before writing a connect/setup/wiring class.

2026-07-150

python-values-failure

kyzodb/kyzo-python

Fires when domain data is about to be shaped wrong instead of as the matching construct in python-values-success — a bare primitive field, an unproven scalar or collection, a T | None absence, free-floating vocabulary, a drifted or unmodeled enum, an after-validator policing a relation the fields should reparameterize, a bare .root held mid-graph, an open (unfrozen or extra-allowing) model, a union alias built without a discriminator, a union wrapped in a class, or a field the ontology never declared.

2026-07-150

python-values-success

kyzodb/kyzo-python

Build the five proven shapes for domain data — semantic scalar, value object, concept model, collection, union. Fires before writing a bare primitive field, a dataclass/NamedTuple/TypedDict, a list/set/dict field, a T | None field, a raw Literal or bare StrEnum field, or a match/if-elif/isinstance ladder selecting by kind.

2026-07-150

python-verbs-failure

kyzodb/kyzo-python

Fires when a model method is about to be written wrong instead of as the matching construct in python-verbs-success — a stub body (raise NotImplementedError/pass/...), a second top-level construction statement in a verb, a verb's signature drifted from its modeled row, a modeled verb missing from the class, a verb/derivation/method with no row authorizing it, an undecorated method on a frozen model, or a verb body that skips a declared constructs/emits participant.

2026-07-150

name	python-state-failure
description	Fires when live state or a transport client is about to land somewhere wrong instead of the matching construct in python-state-success — frozen=True on the consistency model, a client field with no verb emitting through it, or arbitrary_types_allowed=True on any model other than the consistency model.

State — failure patterns

Three ways live state or a transport client escapes the one node allowed to hold it (the consistency model, python-state-success).

Frozen live edge

Freezing the consistency model contradicts what it is: the one node holding live clients and accumulating mutable state. Frozen, it is a different construct wearing the name.

class MarketSession(BaseModel, frozen=True):   # the consistency model is unfrozen; drop frozen=True and add arbitrary_types_allowed=True
    book: CoinbaseBook

Dead handle

A client held on the consistency model but reached by no verb is a capability wired to nothing: structure with no act crossing through it.

class MarketSession(BaseModel):
    coinbase: CoinbaseClient   # no verb ever touches self.coinbase: either a verb must emit through it, or the field is unwired structure

Arbitrary type off the edge

arbitrary_types_allowed anywhere but the one live model lets an unmodeled foreign object sit inside a value: meaning the ontology never described.

class Snapshot(BaseModel):
    model_config = ConfigDict(arbitrary_types_allowed=True)   # legal only on the consistency model
    client: SomeSDKThing   # a live client belongs on the consistency model; foreign data belongs in a foreign model