Repository navigation
Expand file tree
/
Copy pathstatus.yml
More file actions
119 lines (115 loc) · 4.39 KB
/
Copy pathstatus.yml
File metadata and controls
119 lines (115 loc) · 4.39 KB
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
# NetPulse System Implementation Status Manifest
# Single authoritative source of truth for implementation maturity across crates & capabilities.
# Synchronized with documentation via `python scripts/verify_docs_status.py`.
version: 1
last_updated: "2026-10-08"
status_legend:
complete: "✅ Complete"
in_progress: "🚧 In Progress"
planned: "📋 Planned"
crates:
netpulse-core:
layer: Base
design: complete
code: complete
runtime: complete
summary: "Shared data models, traits, error taxonomy, and progressive disclosure levels."
netpulse-platform:
layer: Platform
design: complete
code: complete
runtime: complete
summary: "OS abstractions; Windows Npcap live capture with adapter fallback & socket table behind `live-capture` feature gate."
netpulse-capture:
layer: Ingest
design: complete
code: complete
runtime: complete
summary: "PCAP/PCAPNG file parsing, ring buffer, shedding policy, and deterministic replay complete. Recording exists as a library (Recorder/Recording) but is not yet wired into the shell's live capture loop, which reports that honestly rather than fabricating a recording."
netpulse-capture-svc:
layer: Daemon
design: complete
code: in_progress
runtime: planned
summary: "Privileged capture daemon binary scaffold; frame-handoff IPC daemon planned."
netpulse-decode:
layer: Decode
design: complete
code: complete
runtime: complete
summary: "Zero-copy dissection for Ethernet, IPv4/6, TCP, UDP, ICMP, DNS, HTTP/1.1, TLS complete, fuzzed & hardened against hostile inputs."
netpulse-flow:
layer: Assembly
design: complete
code: complete
runtime: complete
summary: "Bi-directional flow state machine, 5-tuple tracking, and session synthesis."
netpulse-storage:
layer: Persistence
design: complete
code: complete
runtime: complete
summary: "In-memory CaptureStore plus a durable write-behind SQLite mirror: queued writes are drained and barriered, failures must be surfaced (never swallowed), and `PRAGMA integrity_check` runs once per session rather than on every repository connect."
netpulse-narrative:
layer: Presentation
design: complete
code: complete
runtime: complete
summary: "Session-to-story translation engine and progressive disclosure card projection."
netpulse-intel:
layer: Intelligence
design: complete
code: complete
runtime: complete
summary: "Rules-based threat detectors (DNS tunneling, port scans) and anomaly engine."
netpulse-ai:
layer: AI Engine
design: complete
code: complete
runtime: in_progress
summary: "Single egress boundary, grounded retrieval, citation validator, and LocalTemplateBackend complete."
netpulse-learn:
layer: Education
design: complete
code: complete
runtime: complete
summary: "Interactive curriculum engine, Website Load Journey synthesizer, Protocol Explorer reference content, persistent local mastery engine, and interactive lesson player UI."
netpulse-api:
layer: API
design: complete
code: complete
runtime: complete
summary: "v4 DTO IPC contract and TypeScript type drift check."
netpulse-plugin:
layer: Extensibility
design: complete
code: complete
runtime: in_progress
summary: "Extension seam traits, capability model, Ed25519 verifier & registry complete. Trust is derived from verification, never self-declared: the in-tree references ship no signature or hashed payload, so they register as Unreviewed and stay disabled until a user enables them; WASM host planned."
netpulse-engine:
layer: Orchestrator
design: complete
code: complete
runtime: complete
summary: "Offline file analysis and incremental LivePipeline operational; verified against SQLite restart durability and presentation views. The monitoring snapshot projects only the monitor (no narrative/session clones), and attribution is resolved through one shared flow-to-process lookup so the monitoring and security projections cannot disagree."
ui_workspace:
contract:
design: complete
code: complete
runtime: complete
design_system:
design: complete
code: complete
runtime: complete
components:
design: complete
code: complete
runtime: complete
viz:
design: complete
code: complete
runtime: complete
app:
design: complete
code: complete
runtime: complete