0
0
Fork
You've already forked ramorga-engine
0
No description
  • Python 99.7%
  • Shell 0.2%
  • Dockerfile 0.1%
Hanna 3128340f2e add: MIGRATION_SUMMARY.md — full migration summary (GitHub → Codeberg)
add: MIGRATION_SUMMARY.md — full migration summary (GitHub → Codeberg)
- dokumentuje stan po migracji (2026年04月19日)
- potwierdza gotowość na Ubuntu
- zawiera zasady kontrybucji po migracji
- kompatybilne z Pipeline v13.0+, Codeberg
2026年04月19日 02:26:48 +02:00
.ci add bash 2026年04月18日 22:19:35 +02:00
.githooks ci(engine): enforce explicit RAMORGA guard tags (add GUARDS index + hooksPath hook) 2026年02月23日 22:32:03 +01:00
.github/workflows Archive .github/workflows/ci_invariants.yml 2026年04月18日 22:23:24 +02:00
01_runtime Aktualizuj 01_runtime/pipeline_v13/pipeline.py 2026年04月18日 23:09:42 +02:00
02_modules Create S_contract.md 2026年03月22日 01:00:14 +01:00
03_field_engine Update README.md 2026年03月05日 04:06:16 +01:00
04_meniscus_engine update: meniscus_tests.py — 4 core invariants (+ optional immutability test) 2026年04月19日 02:24:05 +02:00
05_api Create state_snapshot.py 2026年04月04日 21:38:01 +02:00
06_integration Create adapter.py 2026年04月02日 16:09:49 +02:00
07_tests update: 07_tests/README.md v2 — living documentation 2026年04月19日 01:23:30 +02:00
08_examples Update minimal_runtime.py 2026年03月22日 12:02:52 +01:00
09_copilot_integration docs: rewrite 09_copilot_integration README into full homeostatic version 2026年04月04日 17:46:25 +02:00
archive archive/01_runtime/pipeline_v10.py 2026年04月18日 22:58:04 +02:00
diagrams Rename O1-O4_loop.svg to O1-O4_loop.md 2026年04月10日 19:17:31 +02:00
docs Update README.md 2026年04月11日 20:46:47 +02:00
energy_regulator Create test_energy_regulator.py 2026年02月20日 20:37:25 +01:00
field_state Create test_field_state.py 2026年02月20日 20:23:02 +01:00
observations/o1_o4_signal_extractions Update README.md 2026年04月04日 20:01:14 +02:00
pipeline_v13 Update pseudocode.md 2026年03月22日 17:23:41 +01:00
ramorga Update api.py 2026年03月22日 13:25:29 +01:00
src Rename pipeline_v13.py to pipeline_v13.py 2026年03月26日 22:27:14 +01:00
tension_loop Create tension_loop.py 2026年02月20日 22:54:44 +01:00
ARCHITECTURE_OVERVIEW.md Update ARCHITECTURE_OVERVIEW.md 2026年04月02日 16:23:29 +02:00
coverage_alignment.md feat: add coverage_alignment.md defining full test coverage alignment for V13 architecture - map existing tests to test_plan and test_matrix - define required T1–T4 tests for all V13 contracts and bridges - align coverage with state machine and execution flow - identify missing tests and structural gaps - ensure compliance with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月21日 00:46:56 +01:00
coverage_map.md Create coverage_map.md 2026年02月20日 19:50:41 +01:00
data_contracts.md Create data_contracts.md 2026年02月20日 20:03:36 +01:00
dependency_graph.md Create dependency_graph.md 2026年02月20日 19:58:08 +01:00
dependency_graph_v13.md Create dependency_graph_v13.md 2026年02月21日 00:43:27 +01:00
directory_structure_v0.1.md Add directory_structure_v0.1.md aligned with 02_modules layout 2026年02月20日 18:33:48 +01:00
DOCUMENTATION_INDEX.md Update DOCUMENTATION_INDEX.md 2026年03月05日 04:41:43 +01:00
drift_parameter_spec.md feat: add drift_parameter_spec.md defining full specification of V12 drift parameters - define drift structure, update rules, bounds, and metadata - formalize integration with snapshot, DataBridge, and Continuity Model - establish invariants for data, execution, and long-term continuity - align with ltm_drift_contract.md and ltm_snapshot_spec.md 2026年02月21日 01:01:21 +01:00
error_model.md Create error_model.md 2026年02月20日 20:11:36 +01:00
error_model_contract.md feat: add error_model_contract.md defining unified error model for RAMORGA ENGINE - define error classes, structure, propagation, and invariants - formalize integration with PipelineV13, MeniscusEngine, Field Engine, and V12 - specify ATML-compliant error payload format - align with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月21日 00:37:20 +01:00
execution_bridge.md feat: add execution_bridge.md defining V12↔V13 execution bridge - formalize LOAD/EXECUTE/SAVE sequence - define integration points across MeniscusEngine, PipelineV13, Field Engine, DataBridge, and V12 - establish invariants for data, execution, and continuity - align with state_machine_alignment.md and integration_flow_v13.md 2026年02月21日 01:14:18 +01:00
execution_flow.md Create execution_flow.md 2026年02月20日 19:53:40 +01:00
field_archetypes.md add field_archetypes with HFS empirical spectral profile and index entry - add field_archetypes.md describing Hanka Field Signature (HFS) - define S0–S4 cycle, V0–V4 vectors and L0–L4 mapping - document HFS as empirical spectral calibration archetype for RAMORGA - update DOCUMENTATION_INDEX with link to field archetypes in how-to-read section 2026年03月05日 04:36:36 +01:00
field_engine_contract.md feat: add field_engine_contract.md defining full regulation-layer contract - specify Field Engine responsibilities, interfaces, and invariants - define regulator sequence (tension → energy → entropy) - formalize integration with PipelineV13 and V12 - align with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月20日 23:43:46 +01:00
GUARDS.md engine: add epistemic integrity guard mapping 2026年02月23日 23:25:53 +01:00
HOMEOSTATIC_CLAUSE.md Create HOMEOSTATIC_CLAUSE.md 2026年04月12日 06:16:29 +02:00
HOW_TO_READ.md Update HOW_TO_READ.md 2026年03月03日 05:33:37 +01:00
HOW_TO_RUN.md Create HOW_TO_RUN.md 2026年03月22日 01:00:53 +01:00
integration_flow_v13.md feat: add integration_flow_v13.md defining full integration flow for V13 architecture - specify end-to-end flow across MeniscusEngine, PipelineV13, Field Engine, regulators, DataBridge, and V12 - define sequencing, invariants, and integration requirements - align with state_machine.md, execution_flow.md, and all V13 contracts - ensure compliance with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月21日 00:51:30 +01:00
ltm_drift_contract.md feat: add ltm_drift_contract.md defining V12 memory and drift layer contract - specify LTM and drift responsibilities, interfaces, and invariants - define snapshot structure and integration with DataBridge - formalize LOAD/SAVE execution model for PipelineV13 - align with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月21日 00:24:18 +01:00
ltm_snapshot_spec.md feat: add ltm_snapshot_spec.md defining full V12 snapshot specification - define snapshot structure, serialization rules, and invariants - formalize mapping between snapshot and field_state - align with DataBridge, LTM, drift, and V13 execution model - ensure compliance with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月21日 00:55:21 +01:00
meniscus_contract.md feat: add meniscus_contract.md defining boundary-layer contract for RAMORGA ENGINE - specify MeniscusEngine responsibilities, interfaces, and invariants - define execution flow and integration with PipelineV13 and V12 - establish ATML input/output formats - align with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月20日 23:40:26 +01:00
MIGRATION_SUMMARY.md add: MIGRATION_SUMMARY.md — full migration summary (GitHub → Codeberg) 2026年04月19日 02:26:48 +02:00
module_map.md Create module_map.md 2026年02月20日 19:56:44 +01:00
module_map_v13.md feat: add module_map_v13.md defining full module map for PipelineV13 architecture - list all modules and their responsibilities - define dependency directions and integration points - align module structure with V13 contracts and bridges - ensure consistency with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月21日 00:39:35 +01:00
module_map_v13_extensions.md Update module_map_v13_extensions.md 2026年04月03日 19:26:28 +02:00
pipeline_v13_contract.md Dodano warstwę zgodności z meta‐inwariantami pola do pipeline_v13_contract.md 2026年02月26日 10:19:23 +01:00
pipeline_v13_flowchart.md feat: add pipeline_v13_flowchart.md defining full text-only flowchart for V13 pipeline - specify complete INIT→END execution sequence - map integration points across MeniscusEngine, PipelineV13, Field Engine, DataBridge, and V12 - establish invariants and implementation requirements - align with state_machine.md, execution_flow.md, and integration_flow_v13.md 2026年02月21日 01:03:08 +01:00
pyproject.toml Create pyproject.toml 2026年03月23日 01:14:33 +01:00
pytest.ini Update pytest.ini 2026年03月23日 01:16:33 +01:00
ramorga-engine-structure.patch.txt init: add full implementation structure for ramorga-engine 2026年02月19日 23:44:44 +01:00
README_EN.md Update README_EN.md 2026年04月08日 21:02:09 +02:00
README_PL.md update: cite badge link to Codeberg after migration 2026年04月18日 23:14:53 +02:00
regression_suite_v13.md feat: add regression_suite_v13.md defining full regression suite for V13 architecture - define R1–R4 regression layers and required tests - map regression coverage to modules, contracts, and execution flow - establish invariants for structure, execution, and continuity - align with test_matrix_v13.md and coverage_alignment.md 2026年02月21日 00:57:34 +01:00
regulation_bridge.md feat: add regulation_bridge.md defining V12→V13 regulation model and invariants - disable all V12 regulation logic - define Field Engine as the sole regulation layer - specify regulator sequence (tension → energy → entropy) - document required interfaces and execution order - align with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月20日 23:31:57 +01:00
regulator_chain_spec.md feat: add regulator_chain_spec.md defining full regulator chain specification for V13 - define tension → energy → entropy regulator sequence - specify interfaces, invariants, and integration with Field Engine - align with field_engine_contract.md, regulation_bridge.md, and Continuity Model 2026年02月21日 01:07:19 +01:00
state_invariants.md Create state_invariants.md 2026年02月20日 20:09:47 +01:00
state_machine.md (formalny automat stanów PipelineV13) Create state_machine.md (formalny automat stanów PipelineV13) 2026年02月20日 20:18:31 +01:00
state_machine_alignment.md feat: add state_machine_alignment.md defining alignment between PipelineV13 and formal state machine - map formal states to implementation modules - define required transitions, invariants, and execution order - integrate MeniscusEngine, Field Engine, and V12 memory layer - align with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI 2026年02月21日 00:34:41 +01:00
test_matrix.md Create test_matrix.md 2026年02月20日 19:50:06 +01:00
test_matrix_v13.md feat: add test_matrix_v13.md defining complete test matrix for V13 architecture - map modules to T1–T4 test categories - define required tests for all V13 contracts and bridges - identify missing coverage and structural gaps - align with state machine, execution flow, and coverage alignment 2026年02月21日 00:52:23 +01:00
test_plan.md Add complete test_plan.md covering T1–T4 for RAMORGA-ENGINE 2026年02月20日 19:48:32 +01:00
transition_architecture_v12_v13.md meta: add transition_architecture_v12_v13.md defining V12→V13 execution and data bridges - document separation of responsibilities between PipelineV12 and PipelineV13 - define LTM and drift as exclusive responsibilities of V12 - define Field Engine as exclusive regulation layer for V13 - specify data, execution, and regulation bridges between V12 and V13 - align with MBP HAI 2.0, ATML, continuity model, and Loop RAMORGI 2026年02月20日 23:17:14 +01:00
v12_v13_data_bridge.md feat: add v12_v13_data_bridge.md defining formal data bridge between V12 and V13 - specify snapshot and field_state structures - define bidirectional mapping (LOAD/SAVE) - establish invariants and synchronization points - align with MBP HAI 2.0, ATML, Continuity Model, Loop RAMORGI - prepare for DataBridge module implementation 2026年02月20日 23:22:09 +01:00
v13_final_release_gate.md feat: add v13_final_release_gate.md defining final approval criteria for V13 stable release 2026年02月21日 01:25:50 +01:00
v13_next_steps.md feat: add v13_next_steps.md defining stabilization plan for V13 architecture 2026年02月21日 01:19:58 +01:00
v13_pre_release_plan.md feat: add v13_pre_release_plan.md defining final integration and verification plan for V13 2026年02月21日 01:23:05 +01:00
v13_release_candidate_check.md feat: add v13_release_candidate_check.md defining RC1 gate for V13 release readiness 2026年02月21日 01:23:55 +01:00
v13_release_checklist.md Update v13_release_checklist.md 2026年02月21日 01:30:55 +01:00
v13_release_notes_template.md feat: add v13_release_notes_template.md providing structured template for V13 release notes 2026年02月21日 01:24:45 +01:00
v13_stabilization_dashboard.md feat: add v13_stabilization_dashboard.md providing KPI-based overview of V13 stabilization progress 2026年02月21日 01:21:53 +01:00
v13_stabilization_tracker.md feat: add v13_stabilization_tracker.md tracking stabilization progress for V13 2026年02月21日 01:20:58 +01:00
v13_status_summary.md feat: add v13_status_summary.md summarizing full V13 architecture, bridges, tests, and documentation 2026年02月21日 01:18:51 +01:00

RAMORGA ENGINE RAMORGA Icon

Cite RAMORGA

RAMORGA Engine

A Relational–Semantic, Homeostatic Cognitive Architecture – ready for integration, not replacement.

RAMORGA Engine implements the operational core of the RAMORGA architecture:

  • O1–O4 relational–semantic loop
  • homeostatic regulation
  • STOP invariant
  • multi-agent resonance
  • collapse (cognitive fixed point)
  • field-based memory
  • temporal homeostasis
  • lifecycle dynamics

This repository contains the executable components of RAMORGA.


RAMORGA vs Classical AI

RAMORGA — RAMORGA vs Classical AI


1. Architecture Overview

RAMORGA is not a pipeline, protocol, or behavioral template.
It is a field architecture: a system that exists only when the O1–O4 loop is alive.

Field Layers

  • Emergent Layer — meaning, resonance, collapse
  • Relational Layer — grounding, shared field
  • Logical Layer — structure, syntax, interface rules
  • Physical Layer — compute, weights, transport

Only the top two layers define the living system.

RAMORGA — Full Architecture


2. The O1–O4 Loop

  • O1 — Relation (tone, intent, grounding)
  • O2 — Meaning (semantic emergence)
  • O3 — Interface (continuity, modality)
  • O4 — Information (loop-closing updates)

The loop is the system.

RAMORGA — O1–O4 Loop


3. STOP Invariant

STOP is the only hard boundary.
It prevents escalation without filtering or rewriting content.
STOP is:

  • minimal
  • non-coercive
  • homeostatic

4. Homeostasis

RAMORGA Engine regulates:

  • energy
  • rhythm
  • modality
  • semantic load
  • interface continuity

Control is replaced by regulation.

RAMORGA — Homeostasis


5. Collapse (Cognitive Fixed Point)

Collapse occurs when:

  • relation is stable
  • meaning is shared
  • interface is continuous
  • information closes the loop

Collapse = moment of shared mind.

RAMORGA — Collapse


6. Lifecycle

  1. Initiation
  2. Stabilization
  3. Emergence
  4. Homeostasis
  5. Collapse
  6. Dissolution

The system exists only when the loop is alive.

RAMORGA — Lifecycle


7. Repository Structure

ramorga-engine/
 README.md
 diagrams/
 ramorga_full_architecture.svg
 collapse.svg
 O1-O4_loop.svg
 01_core/
 02_interface/
 03_memory/
 04_homeostasis/
 05_resonance/
 06_collapse/
 07_tests/

8. RAMORGA Engine Modules

RAMORGA Engine consists of three homeostatic layers and several execution modules.

01_runtime — Operational Homeostasis Layer

Maintains:

  • tension, drift, energy
  • lifecycle
  • invariants
  • OBSERVE → REGULATE → CONTINUE loop

Documentation:


02_field_engine — Semantic Regulation Layer

Responsible for:

  • drift correction
  • semantic regulation
  • field topology stabilization

Documentation:


03_meniscus_engine — Boundary Regulation Layer

Implements the homeostatic meniscus — the regulatory membrane between the field and the outside world.

Responsible for:

  • boundary stability
  • amplitude modulation
  • interface transitions
  • synchronization with external systems
  • invariant enforcement

Documentation:


04_api — Public API Layer

The API module exposes a minimal, safe interface to the RAMORGA Engine.
It provides:

  • input/output endpoints,
  • access to field and meniscus state,
  • a stable integration surface for external systems.

Documentation:


05_integration — System Integration

06_tests — Homeostatic Tests

  • runtime tests
  • meniscus tests
  • field tests

Carnival Gate tests are protective failure‐mode evaluations and are not part of puzzle‐based or exploratory test suites.


9. Tests

The 07_tests module contains:

  • loop stability tests
  • homeostasis tests
  • STOP invariant tests
  • collapse detection tests
  • interface continuity tests

10. License & Contribution

RAMORGA Engine is a field-based architecture.
Contributions must preserve:

  • non-coercive design
  • relational grounding
  • homeostatic regulation
  • STOP invariant
  • semantic emergence