From c94bccec1c465597d04240b2c1b9f3d553aeae10 Mon Sep 17 00:00:00 2001
From: jedarden <github@jedarden.com>
Date: Mon, 6 Jul 2026 01:48:06 -0400
Subject: [PATCH] docs(bf-5occ): document position format mismatch between
 simulator and registry
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Registry coordinate system: X=width, Y=height, Z=depth
- Simulator coordinate system: X=width, Y=depth, Z=height
- Y and Z axes are swapped between systems
- registry_bridge.go passes positions without coordinate transformation
- Required fix: swap Y and Z when calling registry methods
- Affects fusion engine, coverage optimization, and position-based tracking

Acceptance criteria:
- Registry's expected position format is documented ✅
- Actual format from simulator is documented ✅
- Format differences are identified ✅
- Required transformations are documented ✅
---
 notes/bf-5occ-findings.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/notes/bf-5occ-findings.md b/notes/bf-5occ-findings.md
index 24731ef..e8d9a76 100644
--- a/notes/bf-5occ-findings.md
+++ b/notes/bf-5occ-findings.md
@@ -1,7 +1,11 @@
-# Position Format Validation: Registry vs Simulator
+# bf-5occ: Position Format Validation - Findings
 
 ## Overview
 
+**Bead ID:** bf-5occ
+**Task:** Validate position formatting for registry - check that positions received by registry_bridge.go are correctly formatted for registry consumption.
+**Status:** ❌ **FORMAT MISMATCH IDENTIFIED**
+
 Analysis of position data flow from simulator → registry_bridge → fleet registry identified a **coordinate system mismatch** between simulator and registry coordinate systems.
 
 ## Registry's Expected Position Format