runact 1.3.2

A Rust-native actor runtime with BEAM-style processes
Documentation
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
# Runact — Full Development Plan

## 1. Project Vision

Build **Runact** as a Rust-native concurrent runtime and application platform inspired by BEAM, while taking advantage of Rust's ownership, type system, RAII, and zero-cost abstractions.

Runact should eventually provide the foundation for:

* Web applications
* AI agents
* Remote AI agent servers
* PaperOS
* Network services
* Background workers
* CLI applications
* Real-time applications
* Automation systems

The key idea:

> **Runact is one ecosystem, with multiple layers and crates.**

Do not build `runact-web` as an unrelated project.

---

# 2. Overall Architecture

```text
                         RUNACT
                           │
        ┌──────────────────┼──────────────────┐
        │                  │                  │
        ▼                  ▼                  ▼
     Runtime              Web              Process
        │                  │                  │
        │              HTTP/WebSocket        │
        │                  │                  │
        └──────────────────┼──────────────────┘
                           │
                           ▼
                      Runact Net
                           │
                           ▼
                      Operating System
```

More precisely:

```text
Applications
     │
     ├── PaperOS
     ├── AI Agents
     ├── Web Applications
     └── Other Services
     │
     ▼
Runact Application APIs
     │
     ├── Web
     ├── Process
     ├── Networking
     └── Actors
     │
     ▼
Runact Runtime
     │
     ├── Scheduler
     ├── Async Tasks
     ├── Actors
     ├── Supervision
     ├── Timers
     ├── Cancellation
     └── Compute
     │
     ▼
Operating System
```

---

# 3. Repository Structure

Use **one repository and one Cargo workspace**.

```text
runact/
│
├── Cargo.toml
├── README.md
├── LICENSE
│
├── crates/
│   │
│   ├── runact-core/
│   │
│   ├── runact-runtime/
│   │
│   ├── runact-supervision/
│   │
│   ├── runact-compute/
│   │
│   ├── runact-net/
│   │
│   ├── runact-process/
│   │
│   └── runact-web/
│
├── examples/
│   ├── actors/
│   ├── async/
│   ├── tcp-server/
│   ├── http-server/
│   ├── websocket-server/
│   └── ai-agent/
│
├── benchmarks/
│
└── tests/
```

The user-facing crate can eventually be:

```rust
use runact::Runtime;
```

and, when web functionality is enabled:

```rust
use runact::web::App;
```

The internal crates remain modular.

---

# 4. Layer 1 — runact-core

This is the fundamental actor model.

Responsibilities:

```text
Actor
ActorId
Message
Mailbox
ActorContext
Actor lifecycle
Actor errors
Basic handles
```

Do NOT put:

```text
HTTP
TCP
WebSocket
filesystem
processes
```

into `runact-core`.

The core should remain extremely small.

---

# 5. Actor Model

An actor owns its state.

Example:

```rust
struct Counter {
    value: u64,
}
```

Messages:

```rust
enum CounterMessage {
    Increment,
    Get,
}
```

Conceptually:

```text
Actor
 ├── State
 ├── Mailbox
 └── Lifecycle
```

Other actors communicate through messages rather than directly manipulating actor state.

Rust ownership should remain the primary safety mechanism.

Avoid making:

```rust
Arc<Mutex<GlobalState>>
```

the fundamental Runact architecture.

---

# 6. Lightweight Actors

Actors must be lightweight enough to support large numbers of concurrent actors.

Do NOT use:

```text
1 actor = 1 OS thread
```

Instead:

```text
Many Actors
     ↓
Scheduler
     ↓
Small execution slice
     ↓
Worker thread
     ↓
Yield
```

The exact number of actors Runact can support must be established through benchmarks.

---

# 7. Mailboxes

Every actor gets a mailbox.

Requirements:

* bounded
* FIFO by default
* efficient
* thread-safe
* wake-aware
* configurable capacity

Example:

```text
Actor
 │
 └── Mailbox(capacity)
```

When full:

```text
Sender
  ↓
Mailbox full
  ↓
Backpressure
```

Do not use unlimited queues as the default.

---

# 8. Scheduler

Implement a scheduler designed for high concurrency.

Initial architecture:

```text
Scheduler
 ├── Worker 1
 ├── Worker 2
 ├── Worker 3
 └── Worker N
```

Later:

```text
Worker-local queues
        +
Work stealing
        +
Global injection queue
```

Requirements:

* fairness
* low contention
* efficient wakeups
* work stealing
* actor execution budgets
* task scheduling
* no starvation

---

# 9. Cooperative Actor Execution

A single actor must not monopolize a worker.

Use an execution budget inspired by BEAM reductions.

Conceptually:

```text
Actor
 ↓
process messages
 ↓
consume budget
 ↓
budget exhausted
 ↓
yield
 ↓
scheduler
```

Do not copy BEAM's implementation literally.

Develop a Rust-native scheduling model.

---

# 10. Async Runtime

Runact must support standard Rust futures.

The runtime should provide:

```text
spawn()
sleep()
timeout()
cancel()
join()
task_group()
```

Conceptually:

```text
Runact
 ├── Actors
 ├── Async Tasks
 └── Compute Jobs
```

Use actors for stateful concurrent components.

Use async tasks for waiting/I/O.

Use compute jobs for CPU-heavy work.

---

# 11. Future Execution

Runact should be able to poll standard:

```rust
Future<Output = T>
```

without requiring every application to use Tokio.

Task lifecycle:

```text
Created
   ↓
Scheduled
   ↓
Running
   ↓
Waiting
   ↓
Runnable
   ↓
Running
   ↓
Completed
```

Failure:

```text
Running → Failed
```

Cancellation:

```text
Running/Waiting
      ↓
Cancelling
      ↓
Cancelled
```

---

# 12. Waker

Implement a Runact-specific Waker.

Flow:

```text
Future
  ↓
poll()
  ↓
Pending
  ↓
Waker registered
  ↓
I/O/timer/event occurs
  ↓
wake()
  ↓
Task marked Runnable
  ↓
Scheduler
```

Prevent duplicate scheduling using atomic task state.

---

# 13. Cancellation

Cancellation must be cooperative.

Provide:

```rust
CancellationToken
```

with operations such as:

```rust
cancel()
is_cancelled()
```

Use cancellation for:

* requests
* connections
* AI agents
* subprocesses
* background tasks
* shutdown

Never forcibly terminate arbitrary Rust code.

---

# 14. Structured Concurrency

Implement task groups.

Example:

```text
RequestTaskGroup
│
├── Database Task
├── API Task
├── File Task
└── Compute Task
```

If the request is cancelled:

```text
Request cancelled
       ↓
TaskGroup.cancel()
       ↓
Cancel children
```

This is important for the future web framework.

---

# 15. Timers

Implement centralized timers.

Required primitives:

```text
sleep()
timeout()
deadline()
```

Use a simple priority queue initially.

Later evaluate:

```text
timer wheel
```

only if benchmarks justify it.

---

# 16. Compute Pool

CPU-heavy work must not block actor or I/O workers.

Provide:

```rust
runtime.compute(|| {
    expensive_operation()
});
```

Architecture:

```text
Async/Actor Task
       ↓
Compute Job
       ↓
Compute Pool
       ↓
Result
       ↓
Task/Actor
```

Examples:

* parsing
* compression
* hashing
* indexing
* search
* code analysis
* AI preprocessing
* image processing

---

# 17. Fault Isolation

Runact must isolate actor failures.

Example:

```text
Supervisor
│
├── Actor A
├── Actor B
├── Actor C ← panic
└── Actor D
```

Desired behavior:

```text
Actor C panic
      ↓
Catch failure
      ↓
Actor C marked failed
      ↓
Resources cleaned up
      ↓
Supervisor notified
      ↓
Restart / Stop / Escalate
```

A single actor panic should not automatically terminate the entire runtime.

---

# 18. Supervision

Build supervision as a first-class Runact subsystem.

Example:

```text
ApplicationSupervisor
│
├── NetworkSupervisor
├── AgentSupervisor
├── WorkspaceSupervisor
└── WorkerSupervisor
```

Supervisors own the lifecycle policy of their children.

---

# 19. Restart Strategies

Implement initially:

```text
one_for_one
```

Example:

```text
A
B ← fails
C

Only B restarts.
```

Later:

```text
one_for_all
rest_for_one
```

---

# 20. Restart Policies

Support:

```text
Never
OnFailure
Always
```

and limits:

```text
max_restarts
restart_window
backoff
```

Prevent:

```text
crash
restart
crash
restart
...
```

from becoming an infinite restart loop.

---

# 21. Monitoring

Actors should be able to monitor other actors.

Events:

```text
ActorStarted
ActorStopped
ActorFailed
ActorRestarted
ActorTerminated
```

Later add actor links.

---

# 22. Resource Lifecycle

Use Rust ownership and `Drop` heavily.

Example:

```text
Actor
 ├── TCP connection
 ├── file
 ├── temporary data
 └── other resources
```

When the actor terminates:

```text
Actor dropped
     ↓
Rust Drop
     ↓
Resources released
```

This gives Runact a strong combination:

```text
Actor isolation
+
Rust ownership
+
RAII resource cleanup
```

---

# 23. runact-net

Create the networking layer inside the Runact ecosystem.

Responsibilities:

```text
TcpListener
TcpStream
Readiness
Reactor
Async read
Async write
Timeout
Cancellation
Backpressure
```

Linux first:

```text
epoll
```

Later:

```text
kqueue
IOCP
```

Do not initially implement:

```text
HTTP
WebSocket
TLS
DNS
HTTP/2
HTTP/3
QUIC
```

---

# 24. Why TCP Belongs in Runact

Networking is fundamental runtime infrastructure.

Runact needs it for:

```text
Web servers
AI agents
Remote PaperOS
WebSocket services
Custom protocols
Distributed actors
```

Therefore:

```text
runact-net
```

is a natural Runact subsystem.

---

# 25. TCP API

Provide a simple async API:

```rust
let listener = TcpListener::bind("0.0.0.0:8080").await?;

loop {
    let stream = listener.accept().await?;

    runtime.spawn(handle_connection(stream));
}
```

The TCP layer should not care whether the bytes represent:

```text
HTTP
WebSocket
AI protocol
custom binary protocol
```

---

# 26. Network Backpressure

Network buffers must be bounded.

Example:

```text
Application
    ↓
Bounded Buffer
    ↓
TcpStream
    ↓
OS
```

If the client is slow:

```text
write()
 ↓
Pending
 ↓
task yields
```

Do not silently accumulate unlimited response data.

---

# 27. Connection Lifecycle

```text
Accepted
   ↓
Active
   ↓
Reading
   ↓
Processing
   ↓
Writing
   ↓
KeepAlive
   ↓
Closed
```

Failure:

```text
I/O error
   ↓
connection cleanup
```

Cancellation:

```text
Cancel
   ↓
close connection
   ↓
release resources
```

---

# 28. runact-process

Provide process management for AI agents and PaperOS.

Responsibilities:

```text
spawn
stdin
stdout
stderr
exit status
timeout
cancellation
termination
cleanup
```

Architecture:

```text
Runact
  ↓
Process Task
  ↓
Child Process
```

Prevent orphan processes during shutdown.

---

# 29. Integrated Web Layer

Now build:

```text
runact-web
```

**inside the same Runact repository/workspace.**

It is not a separate ecosystem.

Architecture:

```text
runact-web
     ↓
Runact
     ↓
runact-net
     ↓
OS
```

---

# 30. runact-web Responsibilities

`runact-web` owns:

```text
HTTP
WebSocket
Request
Response
Headers
Routing
Middleware
Extractors
Streaming
Cookies
Sessions
Static files
```

Runact owns:

```text
Tasks
Actors
Scheduling
TCP
I/O
Timers
Cancellation
Supervision
Compute
```

---

# 31. HTTP Architecture

A request should flow approximately as:

```text
TCP connection
      ↓
HTTP parser
      ↓
Request
      ↓
Router
      ↓
Middleware
      ↓
Handler
      ↓
Application logic
      ↓
Response
      ↓
HTTP encoder
      ↓
TCP
```

Runact provides the concurrency underneath.

---

# 32. Web Server Concurrency

Example:

```text
WebServer
│
├── Connection Task 1
├── Connection Task 2
├── Connection Task 3
├── Connection Task 4
└── Connection Task N
```

Waiting connections consume very little execution capacity.

Only runnable tasks use workers.

---

# 33. Request Cancellation

If the client disconnects:

```text
Client disconnect
      ↓
Connection cancelled
      ↓
Request TaskGroup cancelled
      ↓
Database/API/File tasks cancelled
      ↓
Resources released
```

This is one of the major reasons Runact's cancellation system must be designed before `runact-web`.

---

# 34. HTTP Handler Model

The eventual API could look like:

```rust
let app = App::new()
    .route("/", get(index))
    .route("/users", get(users))
    .route("/users", post(create_user));

app.listen("0.0.0.0:8080").await?;
```

Do not lock the API too early.

First build the runtime underneath it.

---

# 35. WebSocket

Add WebSocket above TCP:

```text
runact-web
    ↓
WebSocket protocol
    ↓
runact-net
    ↓
Runact reactor
```

WebSocket connections can be represented by:

```text
Connection Task
+
Actor
```

depending on the application's needs.

---

# 36. Middleware

Middleware belongs in `runact-web`.

Examples:

```text
Logging
Authentication
Authorization
Compression
CORS
Rate limiting
Request timeout
Tracing
```

Runact should provide the primitives needed to implement these efficiently, but should not implement web-specific middleware in the runtime.

---

# 37. Streaming

The runtime must support efficient streaming.

Examples:

```text
HTTP streaming
Server-Sent Events
WebSocket streaming
AI token streaming
File downloads
```

Architecture:

```text
Producer
   ↓
Bounded stream
   ↓
Network task
   ↓
TcpStream
```

Backpressure must propagate toward the producer.

---

# 38. AI Agent Server

One of the first serious applications of Runact should be an AI agent server.

Architecture:

```text
Client
  │
  │ HTTP/WebSocket
  ▼
runact-web
  │
  ▼
AgentSupervisor
  │
  └── AgentActor
       │
       ├── LLM Task
       ├── File Task
       ├── Shell Task
       ├── Git Task
       └── Compute Job
```

Runact provides the concurrency and lifecycle management.

---

# 39. PaperOS

PaperOS should eventually use Runact like:

```text
PaperOS
   ↓
Runact
   ↓
Actors
Tasks
Supervision
Networking
Process management
```

Possible actors:

```text
WorkspaceActor
BufferActor
TerminalActor
GitActor
LspActor
AgentActor
ExtensionActor
```

A failing subsystem can be isolated.

---

# 40. Remote PaperOS Agent

Future architecture:

```text
PaperOS Desktop
       │
       │ HTTPS / WebSocket
       ▼
runact-web
       │
       ▼
AgentSupervisor
       │
       ▼
AgentActor
       │
       ├── LLM
       ├── Filesystem
       ├── Shell
       ├── Git
       └── Compute
```

This makes Runact useful beyond traditional web applications.

---

# 41. Security Boundary

Runact should eventually support capabilities.

Examples:

```text
filesystem.read
filesystem.write
network
process.spawn
shell
secrets
```

An AI agent should receive only explicitly granted capabilities.

Example:

```text
Agent
 ├── filesystem.read     ✓
 ├── filesystem.write    ✓
 ├── process.spawn       approval
 ├── network              ✗
 └── secrets              ✗
```

This belongs partly in the application/framework layer, but Runact should provide the lifecycle/resource primitives needed to enforce it.

---

# 42. Observability

Expose runtime metrics:

```text
Actor count
Task count
Runnable tasks
Worker utilization
Mailbox depth
Queue depth
Active connections
Bytes read
Bytes written
Task latency
I/O latency
Actor failures
Restart count
Compute queue depth
```

Do not force one particular observability stack.

Provide instrumentation hooks.

---

# 43. Graceful Shutdown

Runact must support:

```text
Runtime::shutdown()
Runtime::shutdown_with_timeout()
```

Shutdown:

```text
Stop accepting new work
        ↓
Stop accepting new connections
        ↓
Cancel task groups
        ↓
Allow active work to finish
        ↓
Stop actors
        ↓
Close connections
        ↓
Stop async workers
        ↓
Stop compute workers
        ↓
Release resources
```

The runtime must not wait forever.

---

# 44. Testing Strategy

Before building a serious web framework, test Runact itself.

## Actor tests

```text
message delivery
mailbox capacity
actor lifecycle
panic isolation
restart
monitoring
```

## Scheduler tests

```text
fairness
work stealing
starvation
queue contention
```

## Async tests

```text
Future polling
Waker
timeouts
cancellation
task groups
```

## Networking tests

```text
TCP connection
read/write
disconnect
slow client
backpressure
timeouts
cancellation
```

## Process tests

```text
spawn
stdout
stderr
exit
timeout
cancellation
cleanup
```

---

# 45. Fault Injection

Deliberately introduce failures:

```text
Actor panic
Task failure
Connection failure
Client disconnect
Mailbox overflow
Compute queue saturation
Process crash
Timeout
Cancellation
Runtime shutdown
```

Verify:

```text
Unrelated components continue
Resources are released
Supervisor reacts
Restart policy works
Runtime remains consistent
```

---

# 46. Concurrency Benchmark

Build a raw TCP benchmark before HTTP.

Test:

```text
100 connections
1,000 connections
10,000 connections
100,000 connections
```

Measure actual:

```text
Memory
CPU
Latency
Throughput
Wakeup latency
Scheduler latency
```

Do not make performance claims without measurements.

---

# 47. Web Benchmark

After `runact-net` is stable:

```text
runact-web
    ↓
HTTP benchmark
```

Measure:

```text
Requests/sec
P50 latency
P95 latency
P99 latency
Memory per connection
CPU utilization
Concurrent connections
```

Compare against established Rust frameworks/runtimes where useful.

The goal is measurement, not marketing claims.

---

# 48. Development Phases

Development phases are tracked in [Roadmap](roadmap.md). The roadmap is the authoritative source for phase numbering and status.

This document describes the architecture and design. For implementation status, see the roadmap.

### Current Status (v1.2.0)

| Phase | Name | Status |
|-------|------|--------|
| 0 | Architecture | ✅ Complete |
| 1 | Runtime Core | ✅ Complete |
| 2 | Reliability (Supervision) | ✅ Complete |
| 3 | Compute | ✅ Complete |
| 4 | Timers | ✅ Complete |
| 5 | Resources and Capabilities | ✅ Complete |
| 7 | Async Runtime | ✅ Complete |
| 9 | Runtime + Networking | ✅ Complete |
| 10 | HTTP (runact-web) | Next |

### Next Phases

**Phase 10 — HTTP** (see roadmap.md)
- Build `runact-web` as a separate workspace member
- Start with HTTP/1.1, Request, Response, Headers, Parser, Encoder

**Phase 11 — Web Framework** (see roadmap.md)
- Router, Handlers, Middleware, Extractors, Streaming, Static files

**Phase 12 — WebSocket** (see roadmap.md)
- Upgrade, Frames, Connection lifecycle, Streaming, Backpressure, Cancellation

**Phase 13 — Real Applications** (see roadmap.md)
- REST API, WebSocket server, AI agent server, Remote PaperOS server

---

# 49. What NOT to Build in Runact Core

Do not put these into the runtime core:

```text
HTTP
WebSocket
HTML
Templates
REST
GraphQL
Authentication
Cookies
Sessions
ORM
Database abstractions
Business logic
```

They can exist in first-party Runact ecosystem crates.

For example:

```text
runact-web
runact-auth
runact-db
```

but they should remain above the runtime.

---

# 50. Long-Term Ecosystem

Eventually the Runact ecosystem can look like:

```text
                         Runact Ecosystem
                                │
       ┌────────────────────────┼────────────────────────┐
       │                        │                        │
    runact-web              PaperOS                 AI Agents
       │                        │                        │
       │                        │                        │
       └────────────────────────┼────────────────────────┘
                                │
                             Runact
                                │
        ┌───────────────────────┼───────────────────────┐
        │                       │                       │
      Actors                Async Runtime          Compute
        │                       │                       │
        ├──────────────┐        │                       │
        │              │        │                       │
 Supervision        Mailbox   Timers                  Jobs
        │              │        │                       │
        └──────────────┴────────┴───────────────────────┘
                                │
                           runact-net
                                │
                             TCP/I/O
                                │
                                ▼
                               OS
```

---

# 51. The Critical Boundary

Keep this boundary stable:

```text
┌─────────────────────────────────────┐
│           APPLICATIONS              │
│ PaperOS / AI / Web Applications     │
├─────────────────────────────────────┤
│          RUNACT-WEB                  │
│ HTTP / WebSocket / Routing           │
├─────────────────────────────────────┤
│             RUNACT                   │
│ Actors / Tasks / Scheduler           │
│ Supervision / Timers / Cancellation  │
│ Compute / Process / Networking       │
├─────────────────────────────────────┤
│               OS                     │
└─────────────────────────────────────┘
```

The **repository is unified**, but the **architecture is layered**.

---

# 52. Final Principle

Do not think:

> "Runact and runact-web are two different projects."

Think:

> **Runact is the platform. `runact-web` is Runact's web layer.**

Use:

```text
runact
runact-web
runact-net
runact-process
runact-compute
```

as modular crates inside one ecosystem.

The runtime should remain useful without HTTP, while HTTP should be able to exploit every important Runact capability.

---

# 53. Final Goal

The final developer experience should eventually be something like:

```rust
use runact::Runtime;
use runact::web::{App, get};

async fn index() -> &'static str {
    "Hello from Runact"
}

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let runtime = Runtime::new();

    runtime.block_on(async {
        let app = App::new()
            .route("/", get(index));

        app.listen("0.0.0.0:8080").await
    })?;

    Ok(())
}
```

The application developer sees:

```text
Runact
```

not a collection of unrelated runtimes.

Underneath, however:

```text
App
 ↓
HTTP
 ↓
TCP
 ↓
Runact async task
 ↓
Waker
 ↓
Reactor
 ↓
Scheduler
 ↓
Worker
 ↓
OS
```

This is the architecture Runact should be designed toward from the beginning.