Update README.md

README.md

@@ -10,13 +10,13 @@ pinned: false
 license: other
 short_description: NEO alerting-satellite jitter reduction-Starship-style
 ---
-# Rendered Frame Theory (RFT) — Agent Console
+# Rendered Frame Theory (RFT) — Observer Agent Console
 
 I built this Space to be completely open about what I’ve made, how it works, and where it succeeds or fails.
 
-Rendered Frame Theory (RFT) is a framework I developed independently to solve a recurring problem I kept encountering in real predictive systems: most pipelines wait too long to act. They chase certainty, then react. By the time a correction happens, energy has already been wasted, instability has already grown, or the system has already triggered false positives.
+Rendered Frame Theory (RFT) is a framework I developed independently to solve a recurring problem I kept encountering in real predictive systems: many pipelines wait too long to act. They chase certainty, then react. By the time a correction happens, energy has already been wasted, instability has already grown, or the system has already triggered false positives.
 
-RFT flips the priority. It treats timing, uncertainty, and decision “collapse” as first-class variables instead of side effects.
+RFT flips the priority. It treats timing, uncertainty, and decision “commit” (what I call collapse) as first-class variables instead of side effects.
 
 This Space hosts working agents built using that approach. Nothing here is hidden. All code runs. All assumptions are stated. Results are shown honestly, including where the approach does not outperform conventional methods.
 
@@ -34,9 +34,9 @@ Most systems do:
 - correct once confidence is high  
 
 RFT changes the order of importance:
-- predict state and delay  
+- predict state *and* delay cost  
 - estimate uncertainty explicitly  
-- collapse actions earlier when the cost of waiting is higher than the cost of acting  
+- commit actions earlier when the cost of waiting is higher than the cost of acting  
 
 In practice, this can lead to:
 - earlier meaningful corrections  
@@ -44,6 +44,8 @@ In practice, this can lead to:
 - lower compute/actuation usage  
 - more stable behaviour under noise  
 
+**Important wording note:** when I use “observer” in this Space, I mean an explicit decision mechanism (uncertainty → τ_eff → gate → commit/wait). I am not making a claim of machine consciousness here.
+
 ---
 
 ## What this Space is NOT
@@ -61,16 +63,16 @@ It’s a transparent test harness that you can run, break, and compare.
 ## What’s inside
 
 This Space includes:
-- Near-Earth Object (NEO) alerting agent
-- Satellite jitter reduction agent
+- Near-Earth Object (NEO) observer agent (noisy alert filtering)
+- Satellite jitter observer agent (duty reduction / chatter control)
 - Starship-style re-entry & precision landing harness (simplified)
 - A Benchmarks tab with baseline vs RFT runs using the same seed
 - A Theory → Practice page mapping ideas directly to code behaviour
-- A Mathematics tab defining what the variables mean (with units) and how they map into implementation
-- An Investor / Agency walkthrough tab that explains what’s proven here and what’s needed next for production
+- A Mathematics tab defining what the variables mean and how they map into implementation
+- An Investor / Agency walkthrough tab explaining what’s demonstrated here and what would be needed next for production
 
 Every agent:
-- runs locally inside the Space
+- runs inside the Space
 - shows plots
 - exports CSV logs
 - uses reproducible seeds
@@ -79,14 +81,12 @@ Every agent:
 
 ## Why I’m making this open
 
-I’m done hiding behind documents.
+I’m choosing transparency over hype.
 
-If this is “just clever coding”, that will be obvious once people run it.
-If it isn’t, that will also be obvious.
+If this is “just clever coding”, that will be obvious once people run it. If it isn’t, that will also be obvious.
 
-Either way: the code speaks louder than claims.
+Either way, the code and logs speak louder than claims.
 
 Run it. Change parameters. Break it. Compare it.
 
-That’s the standard I’m holding myself to.
-Check out the configuration reference at https://huggingface.co/docs/hub/spaces-config-reference
+(Spaces config reference: https://huggingface.co/docs/hub/spaces-config-reference)