Name: omega-engineering-log
Author: Zynapses

Prompt file imported from Zynapses/Radiant (.windsurf/workflows/omega-engineering-log.md). Copyright stays with the author.

OMEGA Engineering Log Update Policy

When to Update

The OMEGA Engineering Log (apps/omega-proving-ground/OMEGA-ENGINEERING-LOG.md) MUST be updated when:

Any change to omega_core/physics.py — CryoLiquidLayer, HelixKernel, OmegaCortex
Any change to training pipeline — trainer.py, learning rules, loss functions
Any architectural decision — new components, removed components, changed responsibilities
Any experiment result — training runs with metrics, benchmark comparisons
Any new open question — unresolved design decisions that need discussion

What to Update

For architectural decisions:

Add a new entry to ## Decision Log with:

DEC-NNN sequential ID
Status: PROPOSED | AGREED | IMPLEMENTED | REVERTED
Rationale: Why this decision was made
Files modified: What changed

For experiment results:

Add a new entry to ## Experiment Results with:

EXP-NNN sequential ID
Key metrics table
Conclusion

For implementation changes:

Update the ## Implementation Status table.

File Location

apps/omega-proving-ground/OMEGA-ENGINEERING-LOG.md

This file is committed to Git alongside the OMEGA codebase. It travels with the project.

Enforcement

Every PR/commit touching OMEGA files MUST include an engineering log update
AI build agents MUST update the log as part of any OMEGA task
The log is the single source of truth for OMEGA architectural decisions

Install omega-engineering-log and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# OMEGA Engineering Log Update Policy\n\n## When to Update\n\nThe OMEGA Engineering Log (`apps/omega-proving-ground/OMEGA-ENGINEERING-LOG.md`) MUST be updated when:\n\n1. **Any change to `omega_core/physics.py`** — CryoLiquidLayer, HelixKernel, OmegaCortex\n2. **Any change to training pipeline** — `trainer.py`, learning rules, loss functions\n3. **Any architectural decision** — new components, removed components, changed responsibilities\n4. **Any experiment result** — training runs with metrics, benchmark comparisons\n5. **Any new open question** — unresolved design decisions that need discussion\n\n## What to Update\n\n### For architectural decisions:\nAdd a new entry to `## Decision Log` with:\n- **DEC-NNN** sequential ID\n- **Status**: PROPOSED | AGREED | IMPLEMENTED | REVERTED\n- **Rationale**: Why this decision was made\n- **Files modified**: What changed\n\n### For experiment results:\nAdd a new entry to `## Experiment Results` with:\n- **EXP-NNN** sequential ID\n- Key metrics table\n- Conclusion\n\n### For implementation changes:\nUpdate the `## Implementation Status` table.\n\n## File Location\n\n```\napps/omega-proving-ground/OMEGA-ENGINEERING-LOG.md\n```\n\nThis file is committed to Git alongside the OMEGA codebase. It travels with the project.\n\n## Enforcement\n\n- Every PR/commit touching OMEGA files MUST include an engineering log update\n- AI build agents MUST update the log as part of any OMEGA task\n- The log is the single source of truth for OMEGA architectural decisions", "variables": [], "notes": "Policy - OMEGA Engineering Log must be updated when any OMEGA architecture, physics, or training changes are made", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/Zynapses/Radiant", "path": ".windsurf/workflows/omega-engineering-log.md", "ref": "dfcafdfbbf2191ee48921207c5c8a8ca77da957b", "url": "https://github.com/Zynapses/Radiant/blob/dfcafdfbbf2191ee48921207c5c8a8ca77da957b/.windsurf/workflows/omega-engineering-log.md", "key": "Zynapses/Radiant/.windsurf/workflows/omega-engineering-log.md" } } }

omega-engineering-log

About