RFTSystems commited on
Commit
1db85a1
·
verified ·
1 Parent(s): 9d2da30

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +31 -39
README.md CHANGED
@@ -10,7 +10,7 @@ pinned: false
10
  license: other
11
  short_description: NEO alerting-satellite jitter reduction-Starship-style
12
  ---
13
- # Rendered Frame Theory (RFT) — Observer Agent Console
14
 
15
  I built this Space to be completely open about what I’ve made, how it works, and where it succeeds or fails.
16
 
@@ -20,66 +20,58 @@ RFT flips the priority. It treats timing, uncertainty, and decision “commit”
20
 
21
  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.
22
 
23
- ---
24
-
25
- ## What RFT is (in practical terms)
26
 
27
  RFT is not a new programming language, not a replacement for control theory, and not a belief system.
28
 
29
  RFT is a decision-timing framework.
30
 
31
  Most systems do:
32
- - predict state
33
- - minimise error
34
- - correct once confidence is high
35
 
36
  RFT changes the order of importance:
37
- - predict state *and* delay cost
38
- - estimate uncertainty explicitly
39
- - commit actions earlier when the cost of waiting is higher than the cost of acting
40
 
41
  In practice, this can lead to:
42
- - earlier meaningful corrections
43
- - fewer false positives
44
- - lower compute/actuation usage
45
- - more stable behaviour under noise
46
 
47
- **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.
48
-
49
- ---
50
 
51
- ## What this Space is NOT
52
 
53
  This Space is not:
54
- - a certification claim
55
- - a flight-ready aerospace model
56
- - a physics replacement argument
57
- - a “trust me” pitch
58
 
59
  It’s a transparent test harness that you can run, break, and compare.
60
 
61
- ---
62
-
63
- ## What’s inside
64
 
65
  This Space includes:
66
- - Near-Earth Object (NEO) observer agent (noisy alert filtering)
67
- - Satellite jitter observer agent (duty reduction / chatter control)
68
- - Starship-style re-entry & precision landing harness (simplified)
69
- - A Benchmarks tab with baseline vs RFT runs using the same seed
70
- - A Theory → Practice page mapping ideas directly to code behaviour
71
- - A Mathematics tab defining what the variables mean and how they map into implementation
72
- - An Investor / Agency walkthrough tab explaining what’s demonstrated here and what would be needed next for production
73
 
74
  Every agent:
75
- - runs inside the Space
76
- - shows plots
77
- - exports CSV logs
78
- - uses reproducible seeds
79
-
80
- ---
81
 
82
- ## Why I’m making this open
83
 
84
  I’m choosing transparency over hype.
85
 
 
10
  license: other
11
  short_description: NEO alerting-satellite jitter reduction-Starship-style
12
  ---
13
+ Rendered Frame Theory (RFT) — Observer Agent Console
14
 
15
  I built this Space to be completely open about what I’ve made, how it works, and where it succeeds or fails.
16
 
 
20
 
21
  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.
22
 
23
+ What RFT is (in practical terms)
 
 
24
 
25
  RFT is not a new programming language, not a replacement for control theory, and not a belief system.
26
 
27
  RFT is a decision-timing framework.
28
 
29
  Most systems do:
30
+ predict state
31
+ minimise error
32
+ correct once confidence is high
33
 
34
  RFT changes the order of importance:
35
+ predict state and delay cost
36
+ estimate uncertainty explicitly
37
+ commit actions earlier when the cost of waiting is higher than the cost of acting
38
 
39
  In practice, this can lead to:
40
+ earlier meaningful corrections
41
+ fewer false positives
42
+ lower compute/actuation usage
43
+ more stable behaviour under noise
44
 
45
+ 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.
 
 
46
 
47
+ What this Space is NOT
48
 
49
  This Space is not:
50
+ a certification claim
51
+ a flight-ready aerospace model
52
+ a physics replacement argument
53
+ a “trust me” pitch
54
 
55
  It’s a transparent test harness that you can run, break, and compare.
56
 
57
+ What’s inside
 
 
58
 
59
  This Space includes:
60
+ Near-Earth Object (NEO) observer agent (noisy alert filtering)
61
+ Satellite jitter observer agent (duty reduction / chatter control)
62
+ Starship-style re-entry & precision landing harness (simplified)
63
+ A Benchmarks tab with baseline vs RFT runs using the same seed
64
+ A Theory → Practice page mapping ideas directly to code behaviour
65
+ A Mathematics tab defining what the variables mean and how they map into implementation
66
+ An Investor / Agency walkthrough tab explaining what’s demonstrated here and what would be needed next for production
67
 
68
  Every agent:
69
+ runs inside the Space
70
+ shows plots
71
+ exports CSV logs
72
+ uses reproducible seeds
 
 
73
 
74
+ Why I’m making this open
75
 
76
  I’m choosing transparency over hype.
77