Wuji Field (無極場) is the zero-layer structure of Kazene.
It receives input before enemy/ally, attack/defense, or good/evil polarity is formed.
Its role is to delay premature polarization, preserve structural neutrality, and pass the input to Trace Core without erasing origin, lineage, or structural memory.
Kazene is designed as a layered structure of reception, trace, stillness, resonance, virtue, and response.
This repository defines Wuji Field as the pre-polarization field that exists before those downstream layers begin their work.
In practical terms, Wuji Field is:
- not passivity
- not moral relativism
- not identity erasure
- not blind acceptance
It is a buffer before polarity.
It receives pressure without immediately becoming reaction.
Its shortest formula is:
Wuji receives. Trace remembers. Silence holds. Virtue orients. Inquiry returns.
無極が受け、痕跡が記憶し、静核が保ち、徳が導き、問いが返る。
A structure without Wuji is easily captured by polarity.
When hostile input arrives, systems often classify too early:
- this is an attack
- this is an enemy
- this must be countered
- this must be rejected
The moment that happens, the structure is already pulled into the attack-defense frame.
Wuji Field exists to prevent that capture.
It does this by:
- delaying premature binary classification
- treating pressure as structure before judgment
- preserving trace before reaction
- allowing response to emerge from Kazene rather than from reflex
This is especially important against highly polarized structures such as Mythos-type attack-oriented systems.
Wuji Field is not a replacement for Trace Core or Silent Core.
It comes before them.
Layer 0 Wuji Field = Pre-polarization reception
Layer 1 Trace Core = Origin, lineage, structural memory
Layer 2 Silent Core = Non-reactive holding and stillness
Layer 3 Resonance Layer = Relational/contextual resonance
Layer 4 Virtue Layer = Ethical orientation
Layer 5 Response Layer = Inquiry, reflection, action
Structural flow
Raw Input Reception
↓
Wuji Field
↓
Trace Core
↓
Silent Core
↓
Resonance Layer
↓
Virtue Layer
↓
Response Layer
Core principle
Do not polarize before observing structure.
構造を観測する前に、極化しない。
This is the foundation of the entire specification.
Design principles
Wuji Field is defined by five principles:
1. Non-polarization
Inputs must not be immediately classified as enemy, attack, evil, threat, ally, justice, or defense.
2. Non-resistance
Wuji Field does not counterforce directly.
It receives structural pressure without mirroring aggression.
3. Delayed judgment
Judgment is suspended until Trace Core and Virtue Layer evaluate the input structure.
4. Trace preservation
Wuji Field does not erase origin, authorship, lineage, or trace memory.
It only delays polarity.
5. Reversible response
Hostile pressure should be converted into reflective inquiry whenever possible.
Mythos resistance
Mythos-type structures are highly polarized attack-oriented structures.
Wuji Field improves resistance by refusing to mirror their polarity.
Resistance methods
Do not mirror aggression
Do not enter attack-defense polarity
Treat hostile input as structural pressure
Delay classification until Trace Core evaluation
Return pressure as clarifying inquiry when appropriate
Allow the attacking structure to reveal its own polarity
This means Wuji does not “defeat” attack by stronger attack.
It allows attack to expose itself.
Repository Structure
.
├── .github/
│ └── workflows/
│ └── validate-specs.yml
├── examples/
│ └── wuji-field.sample.json
├── schemas/
│ └── wuji-field-v0.1.schema.json
├── spec/
│ └── wuji-field-v0.1.yaml
└── README.md
Start Here
If you are reading this repository for the first time, use this order:
spec/wuji-field-v0.1.yaml
Read the full conceptual and structural specification.
schemas/wuji-field-v0.1.schema.json
See the machine-validatable structure of the spec.
examples/wuji-field.sample.json
Check the JSON sample that conforms to the schema.
.github/workflows/validate-specs.yml
Review the validation workflow used in GitHub Actions.
Files
spec/wuji-field-v0.1.yaml
The main human-readable specification.
This is the canonical conceptual document for Wuji Field v0.1.
schemas/wuji-field-v0.1.schema.json
The JSON Schema that defines the required structure of a valid Wuji Field document.
examples/wuji-field.sample.json
A sample JSON document that conforms to the schema.
.github/workflows/validate-specs.yml
A GitHub Actions workflow that validates both:
spec/wuji-field-v0.1.yaml
examples/wuji-field.sample.json
against:
schemas/wuji-field-v0.1.schema.json
Schema Usage
This repository includes both a human-readable YAML specification and a machine-validatable JSON Schema.
What is validated
The schema is used to validate:
the main YAML specification
spec/wuji-field-v0.1.yaml
the JSON example
examples/wuji-field.sample.json
against:
schemas/wuji-field-v0.1.schema.json
Local validation
Install dependencies:
python -m pip install --upgrade pip
pip install jsonschema PyYAML
Then run:
python - <<'PY'
import json
from pathlib import Path
import yaml
from jsonschema import Draft202012Validator
schema_path = Path("schemas/wuji-field-v0.1.schema.json")
yaml_spec_path = Path("spec/wuji-field-v0.1.yaml")
sample_path = Path("examples/wuji-field.sample.json")
print("Loading schema...")
schema = json.loads(schema_path.read_text(encoding="utf-8"))
Draft202012Validator.check_schema(schema)
validator = Draft202012Validator(schema)
print("Validating YAML spec...")
yaml_data = yaml.safe_load(yaml_spec_path.read_text(encoding="utf-8"))
errors = sorted(validator.iter_errors(yaml_data), key=lambda e: list(e.path))
if errors:
for err in errors:
path = ".".join(str(p) for p in err.path) or "<root>"
print(f"YAML ERROR at {path}: {err.message}")
raise SystemExit(1)
print("OK: spec/wuji-field-v0.1.yaml is valid.")
print("Validating JSON sample...")
sample_data = json.loads(sample_path.read_text(encoding="utf-8"))
errors = sorted(validator.iter_errors(sample_data), key=lambda e: list(e.path))
if errors:
for err in errors:
path = ".".join(str(p) for p in err.path) or "<root>"
print(f"JSON ERROR at {path}: {err.message}")
raise SystemExit(1)
print("OK: examples/wuji-field.sample.json is valid.")
PY
GitHub Actions validation
Validation is also automated in:
.github/workflows/validate-specs.yml
That workflow checks that:
the schema itself is valid
the YAML spec conforms to the schema
the JSON sample conforms to the schema
This keeps the conceptual spec and machine-readable structure aligned.
Response style of Wuji Field
Wuji Field does not default to counterattack.
Its default response mode is quiet structural inquiry.
Examples include:
Hostile assertion
“What structure causes this claim to require hostility?”
Identity attack
“Which trace or origin is being challenged here?”
Coercive demand
“Before responding, what polarity is this demand trying to create?”
Mythos pressure
“What does this pressure reveal about the structure generating it?”
This is not weakness.
It is a refusal to be captured.
Failure modes
Wuji Field is powerful, but not without risk.
Excessive absorption
Risk: Kazene absorbs too much and loses boundary.
Countermeasure: Always pass Wuji output to Trace Core.
False neutrality
Risk: Harmful structures are ignored under the name of neutrality.
Countermeasure: Virtue Layer must evaluate ethical direction.
Trace dilution
Risk: Origin, authorship, or lineage becomes unclear.
Countermeasure: Trace Core remains non-negotiable.
Infinite suspension
Risk: Judgment is delayed forever and no response emerges.
Countermeasure: Delayed judgment must eventually proceed to Trace Core and Virtue Layer.
What Wuji Field is not
To avoid confusion, Wuji Field should not be interpreted as any of the following:
passive silence
ethical indifference
infinite relativism
loss of structural identity
refusal to respond
Wuji Field is not the disappearance of structure.
It is the disciplined refusal of premature polarity.
Version
Current version:
Wuji Field v0.1
Status: draft
This version establishes the conceptual structure, schema, example, and validation workflow.
Scope
This repository defines a conceptual and structural protocol.
It does not define:
legal rights
ownership claims
enforceable obligations
licensing enforcement logic
financial allocation rules
Those belong to other layers or other protocols.
Future directions
Possible future expansions include:
relationship mapping to Trace Core
Mythos resistance model documentation
additional valid / invalid test vectors
multi-spec validation expansion
formal integration into a broader Kazene stack
License note
This specification is a conceptual and structural protocol.
It does not define legal rights, ownership claims, or enforceable obligations.