straddie-makerspace-lab/future.html at main · auraofintelligence/straddie-makerspace-lab · GitHub

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
<!doctype html>
<html lang="en-AU">
  <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <meta name="description" content="Future-facing Sandworm, subterranean, local compute and resilience questions for the Straddie Maker-Space Lab.">
    <title>Future Systems | Straddie Maker-Space Lab</title>
    <link rel="preconnect" href="https://fonts.googleapis.com">
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
    <link href="https://fonts.googleapis.com/css2?family=Atkinson+Hyperlegible:wght@400;700&family=Nunito+Sans:wght@700;800;900&display=swap" rel="stylesheet">
    <link rel="stylesheet" href="styles.css">
    <link rel="icon" href="assets/favicon.svg" type="image/svg+xml">
  <link rel="shortcut icon" href="assets/favicon.ico" type="image/x-icon">
</head>
  <body data-page="future">
    <header data-site-header></header>
    <main id="main">
      <section class="page-hero" aria-labelledby="page-title">
        <div class="page-hero-copy">
          <h1 class="page-title" id="page-title">Which future systems deserve a serious map?</h1>
          <p class="lede">The Sandworm and subterranean city material belongs on the horizon map because it asks a strong question: what tools, skills, data, safety culture and island-built engineering would be needed for future-forward design?</p>
        </div>
        <figure class="page-hero-media">
          <img src="assets/img/future-disaster-kiosk-container.webp" alt="A solar disaster kiosk and local compute node beside a secure container maker-space in Straddie bushland.">
        </figure>
      </section>

      <div class="band-dark">
        <section class="section split" aria-labelledby="boundary-title">
          <div>
            <h2 id="boundary-title">Subterranean is a horizon, not a shortcut.</h2>
            <p class="body-copy">The archive includes bold material about Sandworm tunnelling systems, silica citadels, underground services, local compute, energy storage, permaculture, housing and future resilience. A public proposal can respect the imagination while showing the practical steps that make ambition accountable.</p>
            <p class="open-question">What evidence, prototypes, models, permissions and partners move a future system from story-space into serious public due diligence?</p>
          </div>
          <div class="callout">
            <h3>Reality check</h3>
            <p>Future infrastructure would need cultural authority, land access, engineering design, environmental assessment, geotechnical work, insurance, community support, funding, planning approval and long-term governance. The maker-space can help map those questions without claiming they are solved.</p>
          </div>
        </section>
      </div>

      <section class="section" aria-labelledby="horizons-title">
        <div class="section-head">
          <h2 id="horizons-title">Horizon ideas the maker-space can translate.</h2>
          <p class="body-copy">These ideas become less foggy when they are broken into practical learning questions.</p>
        </div>
        <div class="grid three">
          <article class="info-card"><h3>Sandworm systems</h3><p>What tiny models, boring-head sketches, spoil-handling diagrams and safety questions would help the public understand tunnelling before anyone talks about digging?</p></article>
          <article class="info-card"><h3>Subterranean services</h3><p>The lab can map underground utility ideas as resilience research: cool rooms, storage, conduits, data, shelter, water and maintenance access.</p></article>
          <article class="info-card"><h3>Supercomputers of Straddie</h3><p>What would local compute need to be useful first: noticeboards, digital twins, repair records, sensor logs, training media and disaster information?</p></article>
          <article class="info-card"><h3>Capsule surge lab bridge</h3><p>A future capsule-lab concept can share training, maintenance, local compute and pressure-testing methods with the maker-space.</p></article>
          <article class="info-card"><h3>Mineral moonshot bridge</h3><p>Bigger mineral futures stay in public view through small, safe material demonstrations and source trails.</p></article>
          <article class="info-card"><h3>Local energy literacy</h3><p>Wave, tidal, solar, thermal storage and repair skills can be taught through models before infrastructure decisions are discussed.</p></article>
        </div>
      </section>

      <div class="band">
        <section class="section" aria-labelledby="compute-title">
          <div class="section-head">
            <h2 id="compute-title">What could &quot;supercomputers of Straddie&quot; mean in plain language?</h2>
            <p class="body-copy">A non-technical reader should not be asked to believe in magic hardware. The public version can start with a local knowledge engine: small computers, public screens, repair logs, training videos, project records, sensor data and community memory that work together.</p>
          </div>
          <div class="flow">
            <div class="flow-step"><strong>1</strong><p><b>Local records.</b> Repair cards, experiment notes, tool inductions and safety logs make the lab learn over time.</p></div>
            <div class="flow-step"><strong>2</strong><p><b>Shared screens.</b> Noticeboards, workshop displays and public pages show what is happening without requiring everyone to use developer tools.</p></div>
            <div class="flow-step"><strong>3</strong><p><b>Useful simulations.</b> Simple models can test workshop layouts, waste streams, energy use, visitor flow and emergency tasks before expensive decisions.</p></div>
            <div class="flow-step"><strong>4</strong><p><b>Future compute.</b> Only after practical data exists does bigger compute become more than a shiny box.</p></div>
          </div>
        </section>
      </div>

      <section class="section split reverse" aria-labelledby="future-title">
        <div class="callout">
          <h3>Future-forward, public-safe</h3>
          <p>The best public stance is optimistic and realistic: map the outer edge, name the approvals, invite critique, and keep the first build useful enough that the idea earns attention.</p>
        </div>
        <div>
          <h2 id="future-title">What keeps the big vision honest?</h2>
          <p class="body-copy">A maker-space can become the testing surface for future systems because it is visible. If a concept cannot be explained through a safe model, a material sample, a repair workflow, a public note or a clear question, it probably needs more work before it belongs in a proposal.</p>
        </div>
      </section>
    </main>
    <footer data-site-footer></footer>
    <script src="script.js"></script>
  </body>
</html>