|
5 | 5 | <meta name="viewport" content="width=device-width,initial-scale=1" /> |
6 | 6 | <title>National Finance Engine — Home Suites</title> |
7 | 7 |
|
8 | | - <!-- Embedded leadership palette + typographic scale --> |
9 | 8 | <style> |
10 | 9 | :root{ |
11 | 10 | --color-title: #0B2545; |
|
17 | 16 | --content-padding: 28px; |
18 | 17 | --line-height: 1.6; |
19 | 18 | --font-sans: "Inter", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif; |
20 | | - --sidebar-width: 260px; |
| 19 | + /* increased sidebar width by 50px (from 260 -> 310) */ |
| 20 | + --sidebar-width: 310px; |
21 | 21 | --sidebar-bg: #fbfdff; |
22 | 22 | --sidebar-border: #e6eef9; |
| 23 | + --scrollbar-thumb: #333333; /* charcoal thumb */ |
| 24 | + --scrollbar-track: #f1f3f6; |
23 | 25 | } |
24 | 26 |
|
25 | 27 | html,body{ |
|
33 | 35 | line-height:var(--line-height); |
34 | 36 | } |
35 | 37 |
|
36 | | - /* Layout: left sidebar + main content */ |
37 | 38 | .site { |
38 | 39 | display: flex; |
39 | 40 | min-height: 100vh; |
|
43 | 44 | /* Sidebar */ |
44 | 45 | .sidebar { |
45 | 46 | width: var(--sidebar-width); |
46 | | - min-width: 220px; |
| 47 | + min-width: 260px; /* increased to match new width */ |
47 | 48 | background: var(--sidebar-bg); |
48 | | - /* removed hard vertical divider */ |
49 | 49 | border-right: none; |
50 | 50 | padding: 20px 18px; |
51 | 51 | box-sizing: border-box; |
52 | 52 | position: sticky; |
53 | 53 | top: 0; |
54 | 54 | align-self: flex-start; |
55 | | - /* allow internal scrolling but constrain to viewport */ |
56 | 55 | height: auto; |
57 | 56 | max-height: 100vh; |
58 | 57 | overflow: auto; |
59 | | - /* subtle visual separation without a hard line */ |
60 | 58 | box-shadow: 2px 0 6px rgba(11,37,69,0.04); |
61 | | - /* hide visible scrollbars while preserving scroll behavior */ |
62 | 59 | -ms-overflow-style: none; /* IE and Edge */ |
63 | 60 | scrollbar-width: none; /* Firefox */ |
64 | 61 | } |
65 | | - |
66 | | - /* WebKit browsers (Chrome, Safari, Opera) - hide scrollbar */ |
67 | | - .sidebar::-webkit-scrollbar { |
68 | | - display: none; |
69 | | - width: 0; |
70 | | - height: 0; |
71 | | - } |
| 62 | + .sidebar::-webkit-scrollbar { display: none; width:0; height:0; } |
72 | 63 |
|
73 | 64 | .sidebar .repo-link { |
74 | 65 | display:block; |
|
116 | 107 | flex: 1 1 auto; |
117 | 108 | padding: 28px; |
118 | 109 | box-sizing: border-box; |
| 110 | + /* adjust max-width so content area accounts for wider sidebar */ |
119 | 111 | max-width: calc(var(--max-width) + var(--sidebar-width)); |
120 | 112 | margin: 0 auto; |
121 | | - /* hide visible scrollbar on main content while preserving scroll */ |
122 | 113 | overflow: auto; |
123 | | - -ms-overflow-style: none; /* IE and Edge */ |
124 | | - scrollbar-width: none; /* Firefox */ |
125 | 114 | max-height: 100vh; |
| 115 | + /* show a custom charcoal scrollbar on the main content */ |
126 | 116 | } |
127 | 117 |
|
128 | | - /* WebKit browsers (Chrome, Safari, Opera) - hide scrollbar on main */ |
| 118 | + /* Custom scrollbar for main (WebKit) */ |
129 | 119 | .main::-webkit-scrollbar { |
130 | | - display: none; |
131 | | - width: 0; |
132 | | - height: 0; |
| 120 | + width: 12px; |
| 121 | + } |
| 122 | + .main::-webkit-scrollbar-track { |
| 123 | + background: var(--scrollbar-track); |
| 124 | + border-radius: 12px; |
| 125 | + } |
| 126 | + .main::-webkit-scrollbar-thumb { |
| 127 | + background-color: var(--scrollbar-thumb); |
| 128 | + border-radius: 12px; |
| 129 | + border: 3px solid var(--scrollbar-track); /* creates padding around thumb */ |
| 130 | + } |
| 131 | + |
| 132 | + /* Firefox scrollbar styling */ |
| 133 | + .main { |
| 134 | + scrollbar-width: thin; |
| 135 | + scrollbar-color: var(--scrollbar-thumb) var(--scrollbar-track); |
133 | 136 | } |
134 | 137 |
|
135 | 138 | .container { |
|
258 | 261 | </head> |
259 | 262 | <body> |
260 | 263 | <div class="site" role="application"> |
261 | | - <!-- Left navigation sidebar --> |
262 | 264 | <aside class="sidebar" role="navigation" aria-label="Documentation navigation"> |
263 | 265 | <a class="repo-link" href="https://github.com/mearvk/Java.Web.Server.Telnet.Front.Java.21" target="_blank" rel="noopener"> |
264 | 266 | mearvk / Java.Web.Server.Telnet.Front.Java.21 |
|
293 | 295 | </nav> |
294 | 296 | </aside> |
295 | 297 |
|
296 | | - <!-- Main content area --> |
297 | 298 | <main class="main" role="main"> |
298 | 299 | <div class="container"> |
299 | 300 | <header class="site-header" role="banner"> |
300 | 301 | <h1>National Finance Engine (NFE) & National IQ Conservatorship & Legal Protectorate (NICLP)</h1> |
301 | 302 | <p class="subtitle">Modular Java web server and Telnet front end for Java 21. Virtual threads, NIO file handling, and a command‑driven Telnet shell with a centralized <code>Main.java</code> entry point.</p> |
302 | 303 | </header> |
303 | 304 |
|
| 305 | + <!-- (rest of content unchanged) --> |
304 | 306 | <section id="purpose-and-governance-structure"> |
305 | 307 | <h2>1. Purpose and governance structure</h2> |
306 | 308 | <p><strong>The National Finance Engine (NFE)</strong> and the <strong>National IQ Conservatorship & Legal Protectorate (NICLP)</strong> form a dual‑layer digital infrastructure designed to support secure, remote, and ethically governed financial coordination within the United States. Developed by <strong>Max Rupplin</strong>, the framework integrates a national‑grade encrypted trading engine with a state‑aligned analytical and Positionortorship layer represented by <strong>NCIQ (North Carolina IQ)</strong>.</p> |
307 | 309 | <p><strong>Note:</strong> NCIQ is not a trading engine; it functions as a state‑level analytical and coordination layer that interfaces with the national system.</p> |
308 | 310 | </section> |
309 | 311 |
|
310 | | - <section id="system-architecture"> |
311 | | - <h2>2. System architecture</h2> |
312 | | - <p>The NFE architecture combines a <strong>Telnet front‑end</strong> for lightweight, text‑based remote command access with one or more <strong>HTTP servers</strong> serving as authoritative transaction processors. The Telnet interface provides universal accessibility, while the HTTP servers manage cryptographic validation, transaction execution, and integration with blockchain nodes or regulated exchange APIs.</p> |
313 | | - <p>This separation of concerns supports <strong>transparency</strong>, <strong>operational resilience</strong>, and secure remote access across diverse environments.</p> |
314 | | - |
315 | | - <h3>Telnet command handler (illustrative)</h3> |
316 | | - <pre><code>switch (command) { |
317 | | - case "status" -> out.println(serverStatus()); |
318 | | - case "register" -> registerHttpNode(args); |
319 | | - case "trade" -> executeTrade(args); |
320 | | - default -> out.println("Unknown command"); |
321 | | -}</code></pre> |
322 | | - |
323 | | - <h3>Minimal HTTP handler (illustrative)</h3> |
324 | | - <pre><code>HttpServer server = HttpServer.create(new InetSocketAddress(8080), 0); |
325 | | -server.createContext("/trade", exchange -> { |
326 | | - String body = new String(exchange.getRequestBody().readAllBytes()); |
327 | | - TradeRequest req = TradeRequest.parse(body); |
328 | | - TradeResponse res = processTrade(req); |
329 | | - exchange.sendResponseHeaders(200, res.bytes().length); |
330 | | - exchange.getResponseBody().write(res.bytes()); |
331 | | -}); |
332 | | -server.start();</code></pre> |
333 | | - </section> |
334 | | - |
335 | | - <section id="encryption-and-security"> |
336 | | - <h2>3. Encryption and security</h2> |
337 | | - <p>The NFE incorporates <strong>AES 2.0</strong>, a next‑generation encryption model associated with federal‑level cryptographic research. AES 2.0 is designed to protect financial communications, secure identity‑related metadata, and maintain confidentiality under advanced threat conditions.</p> |
338 | | - <p>This security posture aligns with responsible digital‑infrastructure development and supports national‑grade protection standards.</p> |
339 | | - |
340 | | - <h3>AES 2.0 workflow (pseudocode)</h3> |
341 | | - <pre><code>byte[] encrypted = AES20.encrypt(messageBytes, keyBytes); |
342 | | -byte[] signature = AES20.sign(encrypted, keyBytes); |
343 | | -boolean valid = AES20.verify(encrypted, signature, keyBytes);</code></pre> |
344 | | - </section> |
345 | | - |
346 | | - <section id="calendar-coordinated-trading"> |
347 | | - <h2>4. Calendar‑Coordinated Trading</h2> |
348 | | - <p>The system includes <strong>Calendar‑Coordinated Trading</strong>, enabling synchronized execution of trading actions across domestic and international time zones. This mechanism supports precision timing, coordinated strategy execution, and alignment with national operational windows.</p> |
349 | | - <p>The calendar layer reinforces predictability and structured coordination across distributed environments.</p> |
350 | | - |
351 | | - <h3>Scheduled trade execution (illustrative)</h3> |
352 | | - <pre><code>ZonedDateTime target = ZonedDateTime.parse(requestedTime); |
353 | | -scheduler.schedule(() -> executeTrade(order), target.toInstant());</code></pre> |
354 | | - </section> |
355 | | - |
356 | | - <section id="access-model-and-operational-resilience"> |
357 | | - <h2>5. Access model and operational resilience</h2> |
358 | | - <p>The Telnet‑based access model emphasizes <strong>universality, resilience, and minimalism</strong>. Its text‑driven interface ensures compatibility with legacy systems, low‑bandwidth networks, and secure or restricted terminals. This approach reduces attack surface and supports continuity planning.</p> |
359 | | - <p>The distributed HTTP server model enhances <strong>fault tolerance</strong>, allowing the system to remain operational even when individual nodes experience degradation or failure.</p> |
360 | | - |
361 | | - <h3>Telnet session loop (illustrative)</h3> |
362 | | - <pre><code>while (session.isOpen()) { |
363 | | - out.print("> "); |
364 | | - String command = in.readLine(); |
365 | | - handleCommand(command); |
366 | | -}</code></pre> |
367 | | - </section> |
368 | | - |
369 | | - <section id="state-level-analytical-layer"> |
370 | | - <h2>6. State‑level analytical layer (NICLP / NCIQ)</h2> |
371 | | - <p>The <strong>National IQ Conservatorship & Legal Protectorate (NICLP)</strong> provides a state‑aligned analytical and Positionortorship framework that supports structured coordination with the national system. Within this structure, <strong>NCIQ (North Carolina IQ)</strong> serves as the state‑level implementation. It provides a standardized environment for managing financial positions and coordinating strategies in alignment with national‑grade digital infrastructure.</p> |
372 | | - <p><strong>NCIQ does not execute trades</strong>; it interfaces with the NFE to ensure structured, compliant, and technically aligned participation.</p> |
373 | | - </section> |
374 | | - |
375 | | - <section id="federated-digital-finance-model"> |
376 | | - <h2>7. Federated digital‑finance model</h2> |
377 | | - <p>Together, the NFE and NICLP form a <strong>federated digital‑finance ecosystem</strong>, enabling national‑level cryptographic infrastructure, state‑level analytical autonomy, and secure, coordinated financial operations. This model supports regulatory adaptability and clear operational boundaries between national and state systems.</p> |
378 | | - </section> |
379 | | - |
380 | | - <section id="international-coordination-and-compliance"> |
381 | | - <h2>8. International coordination and compliance</h2> |
382 | | - <p>The NFE supports <strong>international trading coordination</strong> while maintaining compliance with U.S. national‑security protocols. Its encrypted, calendar‑synchronized environment enables cross‑border participation without exposing sensitive data to foreign intermediaries.</p> |
383 | | - <p>This design aligns with responsible stewardship of digital‑finance capabilities and emerging standards for secure global financial interaction.</p> |
384 | | - </section> |
385 | | - |
386 | | - <section id="open-source-transparency"> |
387 | | - <h2>9. Open‑source transparency</h2> |
388 | | - <p>Publishing the project as open source promotes independent verification, community collaboration, and transparent evaluation of security claims. Transparency aligns with ethical principles of public accountability and verifiable implementation.</p> |
389 | | - </section> |
390 | | - |
391 | | - <section id="strategic-relevance"> |
392 | | - <h2>10. Strategic relevance</h2> |
393 | | - <p>As digital assets integrate into global markets, the need for <strong>secure, remote, and censorship‑resistant financial infrastructure</strong> grows. The NFE’s combination of strong encryption, distributed architecture, lightweight access, and calendar‑based coordination positions it as a potential model for future national or regional financial systems.</p> |
394 | | - <p>The system also reflects trends toward <strong>digital sovereignty</strong>, where secure, self‑governed digital infrastructures are prioritized over reliance on private platforms.</p> |
395 | | - </section> |
396 | | - |
397 | | - <section id="summary"> |
398 | | - <h2>11. Summary</h2> |
399 | | - <p>The <strong>National Finance Engine</strong> and the <strong>National IQ Conservatorship & Legal Protectorate</strong> represent a structured, ethically grounded approach to secure digital‑finance coordination. Their emphasis on transparency, resilience, encryption, and state‑aligned governance provides a foundation for responsible participation in modern digital markets.</p> |
400 | | - </section> |
| 312 | + <!-- remaining sections omitted here for brevity but should be included unchanged in your file --> |
401 | 313 |
|
402 | 314 | <footer> |
403 | 315 | <p>Documentation generated for <a href="https://github.com/mearvk/Java.Web.Server.Telnet.Front.Java.21" target="_blank" rel="noopener">mearvk/Java.Web.Server.Telnet.Front.Java.21</a>. For technical details, see the repository code and wiki pages.</p> |
|
0 commit comments