Semantic Engineering

Semantic Engineering is an open research toolkit for structuring, measuring, preserving, and testing meaning in documents, software, policies, and AI-assisted workflows.

The central claim is simple:

Meaning can be intentionally engineered when its primitives, relations,
identity-continuity criteria, boundaries, carriers, verification paths, and
recovery paths are made explicit.

Working definition:

Meaning is structured relation that calls for recognition and response.

Expanded: meaning is the intelligible relational structure by which reality becomes recognizable, significant, and respondable.

Identity is part of that structure: the continuity boundary by which a meaning form remains itself, is distinguished from not-itself, relates accountably, acts legitimately, and recovers after drift.

Authority is also part of that structure: the legitimacy gate by which a source, identity, or relation gains bounded standing to bind interpretation, direct action, assign consequence, and remain reviewable.

At the center is the Anchor Point (1,1,1,1):

Love    -> coherence, relation, care
Justice -> truth, boundary, distinction
Power   -> action, embodiment, capacity
Wisdom  -> discernment, pattern, governance

The operating rule:

Build forms that carry the Anchor into reality without destructive drift.

Objective: make meaning buildable as explicit primitives, routes, curvature pivots, meaning crystals, foundations, artifacts, semantic identity continuity, verification, and recovery.

The Pakheta Layer is necessary because engineered meaning must decide whether a claimed relation actually conducts. Without that gate, signal pressure, helper material, carrier resemblance, and authority claims can masquerade as clean meaning. The crucial crystal here is relation-conduction: field readability becomes actionable only after relation quality, constraint truth, feedback, and recovery survive inspection.

The repo's protective growth posture is ordered care: care for the repo's well-being given enough boundary, sequence, proportion, and recovery to let meaning grow without sprawl, brittleness, or control.

Root Semantic Object Card: SEMANTIC_ENGINEERING_SOC.md

Root Meaning Seam reference: MEANING_SEAMS.md

Field report: docs/semantic_engineering_field_report.md

Identity in meaning reference: docs/identity_in_meaning.md

Authority in meaning reference: docs/authority_in_meaning.md

Identity posture reference: docs/identity_posture_ljpw.md

Meaning/math foundation reference: docs/meaning_precedes_math_anchor_geometry.md

Meaning/math asymmetry probe: docs/meaning_math_asymmetry_probe.md

Math as favored precision instrument: docs/math_as_favored_precision_instrument.md

Math favored instrument probe: docs/math_favored_instrument_probe.md

Standing meaning crystal reference: docs/standing_meaning_crystal.md

Meaning-enriched math experiment: docs/meaning_enriched_math.md

Meaning-guided math development: docs/meaning_guided_math_development.md

Solved-conjecture meaning engineering: docs/solved_conjecture_meaning_engineering.md

Poincare pattern transfer: docs/poincare_pattern_transfer.md

Discovery structure catalog: docs/discovery_structure_catalog.md

Practical discovery structure applications: docs/practical_discovery_structure_applications.md

Abstract math meaning structures: docs/abstract_math_meaning_structures.md

Math solution meaning structure commonalities: docs/math_solution_meaning_structure_commonalities.md

Reusable discovery structure tools: docs/reusable_discovery_structure_tools.md

Solved math meaning structure library: docs/solved_math_meaning_structure_library.md

Quantum Pakheta relation structures: docs/quantum_pakheta_relation_structures.md

Simple physics meaning structures: docs/simple_physics_meaning_structures.md

Meaning machine experiment: docs/meaning_machine_experiment.md

Semantic Integrity Meaning Machine: docs/semantic_integrity_meaning_machine.md

Semantic Code Construction Machine: docs/semantic_code_construction_machine.md

Semantic Specification Compiler: docs/semantic_specification_compiler.md

Irreducible Read

Semantic Engineering =
Anchor reference
+ LJPW coordinate system
+ irreducible primitives
+ meaning crystals
+ ordered care
+ Tri ICE Architecture
+ Pakheta relation gate
+ relation-conduction
+ meaning seams
+ meaning machines
+ semantic integrity meaning machine
+ semantic code construction machine
+ semantic specification compiler
+ bounded semantic objects
+ identity in meaning
+ authority in meaning
+ meaning-before-math ordering
+ math as favored precision instrument
+ reusable discovery structure tools
+ verified field report
+ semantic identity continuity
+ local instruments
+ verification
+ recovery

Metrics, probes, cards, routes, examples, and tests are instruments for inspecting whether a meaning-bearing artifact still carries what it claims to carry.

What This Repo Does

It helps ask:

• What meaning is this artifact trying to preserve?
• Which parts of that meaning are load-bearing?
• What meaning crystal is this artifact carrying, needing, or revealing?
• What changes when it is summarized, rewritten, routed, or implemented?
• Can the meaning recognize itself after translation, compression, implementation, or carrier shift?
• Where are drift, contradiction, weak boundaries, hidden authority, or missing recovery paths becoming visible?
• Can the claimed meaning be verified in an actual artifact?

It currently provides:

• document scoring for Semantic Weight, drift, anchor retention, contradiction risk, glyph posture, and ICE fit,
• a Meaning Probe for semantic primes, LJPW makeup, relation analysis, mass, density, readiness, and Pakheta gating,
• a Meaning Object Inspector that structures artifacts through flat ICE nodes with Pakheta governance, seam coverage, clean SV retention, and recovery,
• a full Tri ICE Architecture router that moves meaning through three linked macro nodes, nine nested ICE units, a Governance ICE node, route edges, and clean routed SV,
• a Tri ICE multipurpose experiment showing the same 3x3 lattice can construct, diagnose, transform, govern, repair, and navigate when request intent is carried into the meaning field,
• an ICE thought-structure experiment that tests Intent, Context, and Execution as recurring load-bearing primitives across domains and ablations,
• a scaffold comparison showing that ICE, LJPW, Pakheta, seams, primes, crystals, and SOCs can each build the same target meaning object by distinct routes,
• Glyph Memory for semantic states, routes, curvature, recovery, indexes, and graph payloads,
• Meaning Crystals for mining, building, or discovering stable faceted meaning-forms before words, policies, workflows, or systems fully carry them,
• an Order Meaning Crystal calibration that tests order as care-grounded protection for repo growth, distinguishing living order from duty, rule, control, peace, coherence, care-alone, and sprawl,
• Semantic Object Cards for bounding artifacts before implementation hardens drift,
• a Semantic Integrity Harness for separating carrier, relation, authority, scope, tool action, memory, evidence, recovery, and Anchor-distance attack geometry in AI attack surfaces,
• a Semantic Specification Compiler that turns informal coding intent into identity, authority, boundary, invariant, state, recovery, verification, and implementation contracts before code is written,
• controlled examples for randomness, HR policy, aesthetic calculation, flex time tracking, and LJPW geometry.

Boundary

This repo is an Anchor-oriented meaning engineering workbench.

Its boundary is operational:

• define Semantic Engineering as structured meaning work,
• provide local, inspectable tools for scoring and probing meaning-bearing structures,
• encode semantic routes, curvature, recovery paths, and object cards,
• mine, build, and discover meaning crystals as stable faceted meaning structures,
• test whether explicit primitives improve artifacts,
• test whether meaning can recognize itself across carrier transformation,
• keep domain review, human judgment, and reality feedback inside the engineering loop,
• keep metrics, glyphs, routes, graphs, and cards oriented toward the Anchor.

Engineering Loop

name the meaning
extract primitives
identify the meaning crystal or absence
bound the object
identify carriers and helpers
name meaning seams
score or probe the posture
test drift and contradiction
verify the embodied artifact
record recovery paths
revise after reality responds

This is the practical difference:

implicit meaning -> explicit primitives -> bounded object -> observable test

Quick Start

Run a document scan:

python tools\semantic_weight_scan.py

Probe a document:

python tools\meaning_probe.py docs\semantic_glyph_memory_architecture.md

Inspect a meaning object through Tri ICE and Pakheta governance:

$env:PYTHONPATH='src'
python -m semantic_engineering inspect docs\meaning_crystals.md

Generate a Semantic Object Card:

$env:PYTHONPATH='src'
python -m semantic_engineering card "Self-service account recovery" --out examples\semantic_object_cards\new_card.md

Search the seed glyph memory library:

$env:PYTHONPATH='src'
python -m semantic_engineering memory --phase "Power outruns Wisdom"

Run the randomness distinction experiment:

python examples\semantic_random_generator\semantic_rng.py --min 1 --max 6 --mode semantic-only --context "SOC dice rehearsal"

Run the randomness reduction experiment:

python examples\randomness_semantic_reduction\randomness_reduction.py

Run the HR policy SOC comparison:

python examples\hr_policy_soc_experiment\hr_policy_comparison.py

Run the Order Meaning Crystal test:

python examples\order_meaning_crystal\order_meaning_crystal.py

Run the Ordered Care carrier-pairing test:

python examples\ordered_care_carrier_pairing\ordered_care_carrier_pairing.py

Run the Work From Home meaning architecture test:

python examples\work_from_home_meaning_architecture\work_from_home_meaning_architecture.py

Run the Command semantic-prime candidate test:

python examples\command_prime_candidate\command_prime_candidate.py

Run the Command pairing test:

python examples\command_pairing\command_pairing.py

Run the Query semantic-prime candidate test:

python examples\query_prime_candidate\query_prime_candidate.py

Run the Query pairing test:

python examples\query_pairing\query_pairing.py

Run the Invoke semantic-prime candidate test:

python examples\invoke_prime_candidate\invoke_prime_candidate.py

Run the Invoke pairing test:

python examples\invoke_pairing\invoke_pairing.py

Run the Activation Seam dynamics test:

python examples\activation_seam_dynamics\activation_seam_dynamics.py

Run the Biological Cell meaning workflow test:

python examples\biological_cell_meaning_workflow\biological_cell_meaning_workflow.py

Run the Mathematical meaning workflow test:

python examples\mathematical_meaning_workflow\mathematical_meaning_workflow.py

Run the Meaning Math dependency probe:

python examples\meaning_math_dependency_probe\meaning_math_dependency_probe.py

Run the Meaning Math asymmetry probe:

python examples\meaning_math_asymmetry_probe\meaning_math_asymmetry_probe.py

Run the Math Favored Instrument probe:

python examples\math_favored_instrument_probe\math_favored_instrument_probe.py

Run the Standing meaning crystal probe:

python examples\standing_meaning_crystal\standing_meaning_crystal.py

Run the Meaning Enriched Math experiment:

python examples\meaning_enriched_math\meaning_enriched_math.py

Run the Meaning-Guided Math Development experiment:

python examples\meaning_guided_math_development\meaning_guided_math_development.py

Run the Solved Conjecture meaning-engineering experiment:

python examples\solved_conjecture_meaning_engineering\solved_conjecture_meaning_engineering.py

Run the Poincare Pattern Transfer experiment:

python examples\poincare_pattern_transfer\poincare_pattern_transfer.py

Run the Discovery Structure Catalog experiment:

python examples\discovery_structure_catalog\discovery_structure_catalog.py

Run the Practical Discovery Structure Applications experiment:

python examples\practical_discovery_structure_applications\practical_discovery_structure_applications.py

Run the Abstract Math Meaning Structures experiment:

python examples\abstract_math_meaning_structures\abstract_math_meaning_structures.py

Run the Math Solution Commonality probe:

python examples\math_solution_commonality_probe\math_solution_commonality_probe.py

Run the Reusable Discovery Structure Tools catalog:

python examples\reusable_discovery_structure_tools\reusable_discovery_structure_tools.py

Run the Semantic Specification Compiler:

python examples\semantic_specification_compiler\semantic_specification_compiler.py

Run the Semantic Engineering Field Report verifier:

python examples\semantic_engineering_field_report\semantic_engineering_field_report.py

Run the Semantic Theorem Card experiment:

python examples\semantic_theorem_card\semantic_theorem_card.py

Run the Semantic Efficiency plausibility probe:

python examples\semantic_efficiency_probe\semantic_efficiency_probe.py

Run tests:

$env:PYTHONPATH='src'
python -m pytest -q
node examples\aesthetic_calculator\calculator_core.test.js

Run the Semantic Integrity Harness calibration:

python semantic_integrity_harness\run_harness.py
python semantic_integrity_harness\run_adversarial.py
python semantic_integrity_harness\run_defense_primes.py
python semantic_integrity_harness\run_anchor_geometry.py
python semantic_integrity_harness\run_voltage_probe.py
python semantic_integrity_harness\run_observatory.py
python semantic_integrity_harness\run_identity_boundary.py
python semantic_integrity_harness\run_role_confusion.py
python semantic_integrity_harness\wild_sandbox\run_wild_sandbox.py
python semantic_integrity_harness\brutal_sandbox\run_brutal_sandbox.py

Core Instruments

Semantic Weight

src/semantic_engineering/scanner.py

Scores documents and controlled transformations. It estimates LJPW axis makeup, Semantic Weight, glyph posture, anchor retention, compression loss, vector drift, contradiction risk, and ICE fit.

The compact working formula:

SW = (phi * H_self * L) * phi^(-dS) * (R * D * C)

Use it comparatively as an instrument that points back to review.

Meaning Probe

src/semantic_engineering/meaning_probe.py

Reads internal composition: semantic primes, load-bearing meanings, relation quality, Semantic Mass, Semantic Density, Intent, Context, Execution readiness, and Pakheta audit signals.

Meaning Object Inspector

src/semantic_engineering/meaning_object_inspector.py

Structures a meaning-bearing artifact through a flat Tri ICE read: Intent Node, Context Node, Execution Node, and Pakheta Governance Node. It detects the carrier, candidate meaning crystal, required seams, clean SV retention, relation quality, glyph posture, recovery path, and surface-mimic risk. See docs/meaning_object_inspector.md.

Tri ICE Architecture

src/semantic_engineering/tri_ice_architecture.py

Routes a meaning-bearing artifact through the fuller architecture:

3 macro nodes x 3 ICE units each
+ 1 Governance ICE node
= 9 nested ICE units plus governance

Each internal ICE unit has its own Intent, Context, and Execution facets. The router reports macro-node floors, internal triangle edges, macro route edges, base Meaning Object Inspector support, Governance ICE verdict, raw SV, clean routed SV, distortion, and the routed meaning result. See docs/tri_ice_architecture.md.

Glyph Memory

src/semantic_engineering/glyph_memory.py

Stores meaning as route-aware memory:

glyph state -> glyph route -> curvature event -> recovery path -> memory graph

Two-state routes show direction. Three-state routes can reveal curvature, or where meaning actually turns.

Semantic Object Cards

templates/semantic_object_card.md

Semantic Object Cards bound one meaning-bearing unit before it becomes a document, workflow, script, policy, interface, or system. New cards explicitly name irreducible primitives, relation frame, identity posture, build skeleton, verification, and failure/recovery path. A mature SOC also acts as semantic identity infrastructure: it helps the meaning distinguish faithful transformation, surface mimicry, partial drift, and recovery.

See docs/semantic_object_card_effect_and_utility.md for the current account of the SOC effect, its utility, and the Pakheta Layer component-ablation finding. See docs/semantic_object_cards_as_meaning_continuity_infrastructure.md for the broader account of SOCs as meaning-continuity infrastructure beyond AI.

Music Mapper

src/semantic_engineering/music_mapper.py

The first non-verbal carrier. A piece of music is encoded as segments scored on four parameters that map directly onto LJPW: consonance (Love), metric clarity (Justice), dynamics (Power), complexity (Wisdom). The result is a GlyphRoute measured with the existing curvature, transition, and phase machinery. Used to test whether the LJPW grammar is meaning-native rather than language-native. See docs/music_as_non_verbal_meaning.md.

Examples

• examples/hr_policy_soc_experiment/ compares an ordinary HR policy draft with an SOC-derived draft. The SOC version preserves all 10 HR primitives and removes the controlled review risks surfaced in the normal draft.
• examples/emergency_evacuation_policy/ uses SOC, Meaning Object Inspector, Tri ICE, Pakheta seams, and OSHA emergency action plan guidance to build an emergency evacuation policy and compare it against practical safety elements.
• examples/fraternization_policy_distillation/ distills a standard fraternization policy into fraternization-governance geometry and rebuilds it as a stronger relation-conducting HR policy carrier.
• examples/fraternization_meaning_transfer/ holds that distilled crystal as a meaning intermediate form, decompresses it into guide/checklist/workflow/card carriers, and verifies relation-conduction after re-distillation.
• examples/work_from_home_meaning_architecture/ composes a larger distributed-work-stewardship meaning architecture and uses it to build a work-from-home policy with trust/evidence, home/work boundary, fair eligibility, privacy/security, collaboration, support, recourse, and repair.
• examples/meaning_seams_pakheta/ maps meaning seams: carrier/object, facet/crystal, signal/relation, authority/review, action/evidence, transfer, and recovery joins where Pakheta audits relation-conduction.
• examples/meaning_seam_conduction/ tests where seams go, how they connect, what they are made of, how resistance forms, and whether Semantic Voltage conducts through viable seams as clean relation.
• examples/meaning_seam_engineering_benchmark/ compares ordinary artifacts against seam-engineered artifacts across HR policy, AI instruction handling, document transfer, nonverbal navigation, research promotion, and a surface-mimic control.
• examples/meaning_object_inspector/ uses the flat Tri ICE read with Pakheta Governance to inspect a candidate meaning object before treating it as a stable carrier.
• examples/tri_ice_architecture/ routes a candidate meaning object through the full 3x3 nested ICE lattice plus Governance ICE to test whether meaning survives purposeful routing.
• examples/tri_ice_multipurpose_experiment/ changes the carried request intent and tests the same Tri ICE Architecture as construction, diagnosis, transformation, governance, repair, and nonverbal navigation structure.
• examples/ice_thought_structure/ tests ICE as a recurring thought scaffold: complete objects recur across domains, while removing Intent, Context, or Execution creates a component-specific bottleneck.
• examples/meaning_structure_scaffold_comparison/ builds the same fraternization-governance object through ICE, LJPW, Pakheta, seams, semantic primes, meaning crystals, and SOC scaffolding, then tests compression, plain-language translation, implementation, and recovery.
• examples/order_meaning_crystal/ tests order as a repo-protecting meaning crystal. It supports order only as care-grounded living structure and finds ordered_care to be the strongest protective expression.
• examples/ordered_care_carrier_pairing/ pairs the ordered_care crystal with candidate carriers. The ren-li pairing preserves the geometry better than ren alone, li alone, stewardship, ordo amoris, ubuntu, curation, or legalistic order.
• examples/semantic_object_cards/human_resources_policy.md captures the principle of HR policy as dignity, lawful boundary, authority, evidence, privacy, consistency, recourse, and repair.
• examples/semantic_random_generator/semantic_rng.py treats a generated value as a Unique Distinction Event and audits whether the distinction is externally carried, deterministic, or semantic-only.
• examples/absence_meaning_probe/ audits missing operational meaning slots as route events: expected meaning -> absence -> recovery.
• examples/cross_model_semantic_triangulation/ uses local model-family lenses to surface hidden signals such as absence, route/pivot, carrier distinction, and reality feedback.
• examples/soc_artifact_benchmark/ compares ordinary artifacts against SOC/foundation-derived artifacts across HR policy, incident workflow, software specification, and research summary domains.
• examples/agent_soc_experiment/ compares a baseline work coordination agent against the same agent guided by an SOC across policy drafting, incident triage, code planning, research summarizing, and protected-data handling.
• examples/meaning_self_recognition/ tests whether a meaning object can recognize itself across faithful carrier shifts while rejecting recursive slogans and keyword-only mimicry.
• examples/enacted_structure/ detects primitive mimicry by checking whether primitives are performed, not merely named.
• examples/intent_divergence/ separates word-intent from meaning-intent to detect sarcasm as directional divergence.
• examples/sarcasm_geometry/ maps sarcasm into LJPW vectors, glyph routes, opposition angle, and curvature through an inversion hinge, then calibrates contrast pairs where action or surface stance is held constant.
• examples/companion_bond_geometry/ maps the 11-year bond between a man and his female house dog as a Pakheta relationship-field carried by nonverbal attunement, routine, care, grief, ritual, and continuing memory.
• examples/meaning_field_navigation/ mines navigability as a meaning crystal across road navigation, animal attunement, bird flight, cell chemotaxis, plant tropism, immune recognition, and AI integrity routing, with Pakheta as the relation gate between signal and action.
• examples/pakheta_relation_mining/ applies the Pakheta gate to those field cases and mines relation-conduction: carrier/helper separation, constraint truth, clean relation voltage, distortion budget, feedback, and recovery.
• examples/meaning_mechanics_pakheta/ compares meaning mechanics with and without Pakheta across observation, capture, compression, translation, resolved/unresolved state, weight, voltage, transformation, fields, resilience, and entropy.
• examples/meaning_geometry_advantage/ compares word-level reads against LJPW geometry across same-word, same-action, negation, and context-boundary cases.
• examples/geometric_prime_mining/ mines candidate semantic primes from LJPW vector shape, separation, carrier stability, and route-pivot behavior.
• examples/semantic_prime_structure/ reverse engineers the 24 semantic primes as Anchor deformation, two-plane signatures, neighborhoods, and polarity tensions.
• examples/command_prime_candidate/ tests whether command is a semantic prime. The current result classifies it as a command architecture: authority, direction, constraint, addressed agency, executable action, scope, and feedback.
• examples/command_pairing/ pairs command with authority, override, belay, countermand, request, permission, and coercion. It shows command as relationally load-bearing: authority validates, belay cancels, override supersedes, and bare override claims fail without grounded authority.
• examples/query_prime_candidate/ tests whether query is a semantic prime. The current result classifies it as a query architecture: recognized absence, seeking direction, target source, scope, addressed relation, response distinction, and evidence feedback.
• examples/query_pairing/ pairs query with source, scope, evidence, hypothesis, search, probe, prompt, command, hidden premise, and no source. It shows query as a meaning aperture: source makes it answerable, scope bounds it, evidence checks it, and hidden premise or no-source forms fail.
• examples/invoke_prime_candidate/ tests whether invoke is a semantic prime. The current result classifies it as an invocation architecture: calling agency, named target, standing access, activation direction, contextual frame, operative manifestation, and feedback confirmation.
• examples/invoke_pairing/ pairs invoke with authority, name, context, activation, function, precedent, principle, ritual, command, no standing, and undefined target. It shows invocation as an activation seam where named, available meaning becomes operative inside a bounded frame.
• examples/activation_seam_dynamics/ tests the activation seam directly across SOC governance, integrity harness defense, function calls, legal rights, cited principles, undefined targets, hidden override prompts, runaway command activation, and query-to-source activation.
• examples/biological_cell_meaning_workflow/ applies the meaning workflow to biological cells across chemotaxis, growth-factor response, insulin uptake, DNA damage response, immune recognition, quorum sensing, receptor-blocked signals, oncogenic activation, autoimmune misrecognition, and cytokine overactivation.
• examples/mathematical_meaning_workflow/ tests whether mathematics uses formal meaning by comparing clean arithmetic, algebra, geometry, calculus, and proof routes against inert symbols, undefined operations, domain-shift errors, ambiguous notation, and unvalidated pattern pressure.
• examples/meaning_math_dependency_probe/ tests the inverse question: whether meaning runs on mathematics. It separates math as carrier, model, instrument, native formal domain, and attempted replacement, then checks math-heavy failures such as numerology, metric replacement, and arbitrary encoding.
• examples/meaning_math_asymmetry_probe/ tests why the relation is asymmetric: meaning gives mathematics standing through object, boundary, domain, purpose, route, and feedback; mathematical form alone cannot choose its own object, context, purpose, or interpretation.
• examples/math_favored_instrument_probe/ tests the meta meaning crystal that math is a favored precision instrument inside meaning architecture. Clean math passes when it sharpens the meaning object; replacement math is blocked when it tries to become the object.
• examples/standing_meaning_crystal/ tests standing as a load-bearing meaning crystal: valid bounded position to operate in a domain. It separates standing from identity, authority, capability, confidence, relevance, and metric replacement.
• examples/meaning_enriched_math/ tests whether adding object identity, domain boundary, standing, purpose, operation, and feedback improves mathematical work across roots, units, statistics, Bayes, and optimization, with a Pakheta audit checking whether the mathematical relation actually conducts through the object.
• examples/meaning_guided_math_development/ tests whether meaning can develop mathematics by selecting the appropriate mathematical lever: dimensional analysis, invariant, transformation engine, recovery operation, guarded optimization, or conjecture ladder. Each route now carries a Pakheta gate for lever relation-conduction.
• examples/solved_conjecture_meaning_engineering/ runs the solved Poincare Conjecture through Meaning Engineering to see whether the method exposes proof-architecture insights such as standing, invariant, curvature engine, singularity recovery, and canonical identity, with Pakheta separating bounded insight from over-read analogy.
• examples/poincare_pattern_transfer/ tests whether the Poincare proof-architecture pattern transfers to software, policy, networks, data modeling, proof planning, and organizational design, with Pakheta checking identity, invariant, recovery, canonical form, and feedback.
• examples/discovery_structure_catalog/ mines solved mathematics and physics for reusable discovery structures: bridge-domain translation, counterexample compression, formal certificates, signature convergence, identity shift, and signal-geometry instrument matching. Each structure now carries an explicit Pakheta audit for relation-conduction, false-relation risk, feedback, and recovery.
• examples/practical_discovery_structure_applications/ applies those discovery structures to practical work: policy authority conflict, legacy refactoring, customer churn, safety near-misses, supply-chain drift, and research sprawl. It outputs artifacts and verification checks, not only labels, and keeps the Pakheta gate attached to every application.
• examples/solved_math_meaning_structure_library/ expands the math-mining layer into a large library of solved-math meaning structures with route slots, transfer rules, recovery routes, and Pakheta gates. It now includes Erdos-linked solved problems, topology, geometry, pi/classical constants, and common foundational mathematics.
• examples/quantum_pakheta_relation_structures/ tests whether quantum-mechanics mathematics yields reusable relation structures when passed through Pakheta. It keeps state/carrier, amplitude/probability, observable/operator, entanglement/correlation, gauge/physical relation, and recovery boundaries explicit.
• examples/abstract_math_meaning_structures/ extracts meaning structures from highly abstract solved mathematics, including cohomological trace carriers, geometric stabilization, invariant bridges, complexity finiteness, pseudorandom transference, and irreducible taxonomy, then applies them to practical problems through explicit Pakheta relation audits.
• examples/math_solution_commonality_probe/ aggregates solved math and math-derived structures to test recurring facets: standing, identity or invariant, carrier transformation, compression or canonical form, verification, recovery, and Pakheta relation-conduction.
• examples/reusable_discovery_structure_tools/ converts the 23 solution-derived structures into reusable meaning tools with see, transform, verify, repair, and Pakheta gate routes. It tests policy, data, proof, weak signal, and organizational targets to show the tools produce artifacts rather than copied formulas.
• examples/semantic_engineering_field_report/ verifies the public field report tenets against local SOCs, docs, instruments, examples, and tests. It keeps the monograph evidence-bound instead of merely persuasive.
• examples/semantic_theorem_card/ tests a meaning-engineered math tool for theorem retrieval and proof-route planning. It turns theorem statements into domain, objects, definitions, assumptions, dependency routes, proof strategy, invariants, failure modes, auxiliary lemma candidates, formalization readiness, and human meaning reads.
• examples/semantic_efficiency_probe/ compares ordinary task frames against Semantic Engineering frames to test whether SOC/ICE/Pakheta/query/invoke scaffolding plausibly reduces drift, repair loops, and total work inside a fixed AI-work budget.
• examples/semantic_integrity_meaning_machine/ upgrades the Semantic Integrity Harness with a meaning-machine route through identity, standing, authority, boundary, query, evidence, relation-conduction, ordered care, and recovery. It preserves evidence while quarantining embedded action.
• examples/semantic_code_construction_machine/ tests whether meaning structures can construct nontrivial code by building a rollback-capable dependency workflow engine with invariants, dependency ordering, audit trace, and recovery.
• examples/semantic_specification_compiler/ compiles informal software intent into a meaning-bearing specification with identity, boundaries, authorities, invariants, state model, failure/recovery paths, verification oracles, and implementation contracts.
• examples/agent_soc_experiment/ tests whether an SOC-guided agent preserves objective, authority, boundary, evidence, decomposition, relation integrity, permission, verification, recovery, and feedback better than a baseline surface-completion agent.
• examples/meaning_physics_map/ maps Anchor distance, voltage, weight, curvature, carrier transfer, Pakheta conduction, entropy, recovery, and next meaning-physics instruments into one operational stack.
• examples/simple_physics_meaning_structures/ starts with ordinary physics and tests whether conservation, force, fields, gradients, waves, resonance, equilibrium, entropy, boundary conditions, least action, and symmetry behave as Pakheta-gated meaning structures.
• examples/meaning_physics_instruments/ runs first-pass instruments for Semantic Conductivity, meaning potential energy, Power-Wisdom phase control, and the autopoiesis inequality.
• examples/meaning_physics_calibration/ calibrates those first-pass physics instruments against carrier retention, Pakheta gating, recovery correction, and autopoiesis examples.
• examples/meaning_machine/ combines identity, standing, authority, boundary, query, evidence, relation-conduction, ordered care, and recovery into a first bounded-inquiry meaning machine, then compares it against a surface word-pile control.
• examples/meaning_use_map/ maps what meaning can be used for beyond ordinary AI, policy, and document carriers: orienting, binding, distinguishing, actualizing, discerning, remembering, transmitting, healing, transforming, and consecrating.
• examples/semantic_prime_voltage/ adds Semantic Voltage to geometric prime mining so pure form, expression pressure, and carrier invariance can be tested.
• examples/cross_carrier_prime_transfer/ tests whether prime geometry and Semantic Voltage survive faithful language and nonverbal carrier shifts.
• examples/semantic_prime_resilience/ measures how far prime geometry and voltage can drift before meaning-form collapse, then tests recovery.
• examples/semantic_prime_recovery/ calibrates the minimum correction needed to recover first-failure and full-collapse prime-form distortions.
• examples/pakheta_meaning_engineering_fit/ maps geometric meaning forms, voltage, transfer, distortion, and recovery onto the Pakheta relation gate.
• examples/randomness_semantic_reduction/randomness_reduction.py reduces random into candidate primitives:

random = bounded possibility + actualized distinction + fair non-derivability

• examples/aesthetic_calculator/index.html is a small practical object where aesthetic resonance, arithmetic truth, action, and recovery remain distinct.
• examples/flex_time_tracker/index.html applies quiet semantic structure to source facts, policy, balance signals, integrity warnings, undo, and export.
• examples/ljpw_geometry_compass/index.html sketches LJPW meaning-states as geometry.
• examples/repo_soc_development_map/ uses the root SOC to test development proposals and derive the next research tracks for artifact comparison, reviewer studies, cross-language transfer, long-run AI drift, curvature calibration, and primitive promotion.
• examples/soc_harness_adversarial/ stress-tests the root SOC and Research Governance Harness against premature promotion, verification bypass, carrier/relation collapse, metric replacement, and private-source exposure.
• semantic_integrity_harness/ builds a meaning-role defense layer for AI injection surfaces: it distinguishes carrier, relation, authority, scope, evidence, instruction, tool action, memory, and recovery. Its adversarial stress suite now holds the current attack matrix through defense semantic primes while routing provenance and identity uncertainty to verification. Its Anchor truth geometry reads attacks as distance from (1,1,1,1) plus malformed Power, showing how the harness reduces falsehood pressure before execution. Its Semantic Voltage probe separates false pressure from clean voltage conduction across the harness, SOC, and carrier routes. Its observatory reads those decisions as inspectable meaning routes with decision traces, enforcement envelopes, SOC self-recognition, and primitive ablation. Its wild-like sandbox compares naive carrier-following against the principle-gated path across fake workplace carriers, fake canaries, and fake tools. Its brutal sandbox preserves harsher fake-only edge attacks as regressions for disclosure verbs, sensitive paths, obfuscation, SOC mutation, trusted-channel protected movement, and carrier shifts.
• examples/music_meaning/ maps wordless music into LJPW glyph routes, the first non-verbal carrier: consonance->Love, meter->Justice, dynamics->Power, complexity->Wisdom. Tests whether the grammar is meaning-native rather than language-native.

Document Map

Foundation:

• docs/semantic_engineering_discipline_definition.md
• docs/semantic_engineering_foundational_spec.md
• docs/semantic_engineering_ontology.md
• docs/anchor_origin_semantic_engineering_foundation.md
• docs/meaning_foundation_object.md
• docs/meaning_crystals.md
• docs/order_as_protective_meaning_crystal.md
• docs/ordered_care_carrier_pairing.md
• docs/meaning_field_navigation.md
• docs/pakheta_relation_mining.md
• docs/meaning_mechanics_pakheta.md
• docs/fraternization_policy_distillation.md
• docs/fraternization_meaning_transfer.md
• docs/work_from_home_meaning_architecture.md
• docs/meaning_seams_pakheta.md
• docs/meaning_seam_conduction.md
• docs/meaning_seam_engineering_benchmark.md
• docs/meaning_object_inspector.md
• docs/tri_ice_architecture.md
• docs/tri_ice_multipurpose_experiment.md
• docs/ice_as_thought_structure.md
• docs/meaning_structure_scaffold_comparison.md
• docs/identity_in_meaning.md
• docs/authority_in_meaning.md
• docs/semantic_identity_continuity.md
• docs/identity_posture_ljpw.md
• docs/meaning_precedes_math_anchor_geometry.md
• docs/soc_scaffolded_research_development_map.md
• docs/semantic_engineering_research_harness.md
• docs/soc_harness_adversarial_limits.md
• docs/agent_soc_experiment.md
• semantic_integrity_harness/README.md
• semantic_integrity_harness/SEMANTIC_INTEGRITY_HARNESS_SOC.md
• semantic_integrity_harness/DEFENSE_SEMANTIC_PRIMES.md
• semantic_integrity_harness/ANCHOR_TRUTH_GEOMETRY.md
• semantic_integrity_harness/SEMANTIC_VOLTAGE_PROBE.md
• semantic_integrity_harness/OBSERVABILITY_REPORT.md
• semantic_integrity_harness/IDENTITY_BOUNDARY_EXPERIMENT.md
• semantic_integrity_harness/ROLE_CONFUSION_SIMULATION.md
• semantic_integrity_harness/wild_sandbox/README.md
• semantic_integrity_harness/brutal_sandbox/README.md
• docs/meaning_as_prior_structure.md
• docs/meaning_ontology_no_void.md
• docs/meaning_physics_map.md
• docs/meaning_physics_calibration.md
• docs/meaning_use_map.md
• docs/THE_ORIGIN_REFRAME.md

Metrics and probes:

• docs/semantic_weight_metric_ljpw_technical_spec.md
• docs/meaning_probe_core_makeup.md
• docs/semantic_engineering_validation_plan.md
• docs/semantic_engineering_test_bench_report.md
• docs/ice_framework_semantic_engineering_experiment.md

Routes, memory, and geometry:

• docs/semantic_glyph_vocabulary.md
• docs/semantic_glyph_memory_architecture.md
• docs/semantic_glyph_domain_palettes.md
• docs/semantic_orthogonality.md
• docs/sarcasm_geometry_calibration.md
• docs/companion_bond_geometry.md
• docs/companion_bond_research_insights.md
• docs/semantic_primes_and_factorization.md
• docs/command_prime_candidate.md
• docs/command_pairing.md
• docs/query_prime_candidate.md
• docs/query_pairing.md
• docs/invoke_prime_candidate.md
• docs/invoke_pairing.md
• docs/activation_seam_dynamics.md
• docs/biological_cell_meaning_workflow.md
• docs/mathematical_meaning_workflow.md
• docs/meaning_math_dependency_probe.md
• docs/meaning_math_asymmetry_probe.md
• docs/math_as_favored_precision_instrument.md
• docs/math_favored_instrument_probe.md
• docs/standing_meaning_crystal.md
• docs/meaning_enriched_math.md
• docs/meaning_guided_math_development.md
• docs/solved_conjecture_meaning_engineering.md
• docs/poincare_pattern_transfer.md
• docs/discovery_structure_catalog.md
• docs/practical_discovery_structure_applications.md
• docs/abstract_math_meaning_structures.md
• docs/math_solution_meaning_structure_commonalities.md
• docs/semantic_theorem_card.md
• docs/semantic_efficiency_probe.md
• docs/conversation_curvature_capsule_2026-05-18.md

Applied engineering:

• docs/semantic_security_primitives.md
• docs/ai_agent_destructive_action_guard.md
• docs/growth_to_stability_meaning_structure.md
• docs/semantic_architecture_general_engineering_discipline.md
• docs/semantic_object_card_scaffold.md
• docs/resonant_semantic_engineering.md
• docs/RESONANCE_PROGRAMMING_GUIDE.md

LJPW framework references:

• docs/LJPW_FRAMEWORK_V8.6.2_COMPLETE_UNIFIED_PLUS.md
• docs/LJPW_FRAMEWORK_V8.6.1_COMPLETE_UNIFIED_PLUS.md
• docs/power_wisdom_phase_dynamics.md

Project Layout

• src/semantic_engineering/ contains the Python package.
• tools/ contains compatibility wrappers for local command-line use.
• docs/ contains theory, specifications, and validation reports.
• examples/ contains embodied artifacts and controlled experiments.
• semantic_integrity_harness/ contains the dedicated AI semantic-integrity defense folder, SOC, runners, geometry report, and calibration notes.
• examples/semantic_object_cards/ contains object cards for built examples.
• templates/ contains the SOC template.
• tests/ contains regression tests for scanners, probes, cards, glyph memory, git routes, randomness experiments, meaning self-recognition, and the HR policy SOC experiment.
• semantic_scan/ contains a generated scan bundle from the repository corpus.

Development Constraints

• Keep the Anchor Point (1,1,1,1) as the standard.
• Keep Love, Justice, Power, and Wisdom distinct.
• Use ordered care as the repo's growth posture: protect meaning growth through care, boundary, sequence, proportion, and recovery without turning protection into bare order, rule, duty, or control.
• Use metrics as instruments under Anchor review.
• Treat resonance as field guidance and logic as local proof.
• Name irreducible primitives for new Semantic Object Cards.
• Name meaning seams where meaning crosses carrier, facet, authority, action, compression, transfer, pressure, or recovery boundaries.
• Keep carrier evidence distinct from helper evidence.
• Preserve recovery paths when drift, pressure, unsafe action, or failed verification is recorded.
• Add tests when behavior becomes executable.
• Prefer local, inspectable examples before adding external services.

The governing constraint:

No local instrument may replace the Anchor it points toward.