{stage.name}
+ {stage.phase} +{stage.detail}
+{stage.id}
+ diff --git a/website/src/components/landing/ClosingSection.astro b/website/src/components/landing/ClosingSection.astro
new file mode 100644
index 00000000..dea0c78b
--- /dev/null
+++ b/website/src/components/landing/ClosingSection.astro
@@ -0,0 +1,20 @@
+ 04 / RUN IT The CLI currently registers the JVM stack and runs it from a YAML configuration. Start at the source, then tune each transform around the application’s real ABI.
+ NekoObfuscator composes dependency-aware bytecode transforms, binds protected data to live control flow, and can translate selected methods into native libraries.
+ Protect the graph,
+
not just the names.
+ Destroy the
+ static shape
+ of Java.
+
+
+
+ Candidate methods pass a safety checker, translate into generated C, compile through Zig for configured targets, and return to the JAR as platform libraries with runtime loading and binding support. +
+EMITTED TARGETS
+› safety-check selected methods
+› generate sliced C source set
+› zig cc -O3 -shared -target …
+› pack /neko/native/libneko_*
+✓ runtime loader installed
+02 / ACTUAL PASS ORDER
+These are the passes registered by the CLI today, in the order exposed by the codebase.
+{stage.detail}
+{stage.id}
+ 01 / PROTECTION SYSTEM
+The strongest parts of the current implementation are connected: later transforms consume metadata and keys produced by earlier passes.
+{layer.description}
+