-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathloop.html
More file actions
101 lines (84 loc) · 8.33 KB
/
Copy pathloop.html
File metadata and controls
101 lines (84 loc) · 8.33 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
<!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="A lawful pre-tip diversion workflow for repair, reuse, parts, material stock and approved recycling pathways.">
<meta property="og:title" content="Lawful Loop Design | Straddie Tip Loop Lab">
<meta property="og:description" content="A lawful pre-tip diversion workflow for repair, reuse, parts, material stock and approved recycling pathways.">
<meta property="og:image" content="assets/img/heroes/lawful-loop-design.webp">
<meta property="og:url" content="https://auraofintelligence.github.io/straddie-tip-loop-lab/loop.html">
<title>Lawful Loop Design | Straddie Tip Loop 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="loop">
<header data-site-header></header>
<main id="main">
<section class="page-hero" aria-labelledby="page-title">
<figure class="page-hero-media" aria-hidden="true">
<img src="assets/img/heroes/lawful-loop-design.webp" alt="">
</figure>
<div class="page-hero-inner">
<div class="page-hero-copy">
<h1 class="page-title" id="page-title">Could value move before waste?</h1>
<p class="lede">The loop starts with permission, supervision and clear choice paths, not with scavenging by default.</p>
<div class="button-row"><a class="button primary" href="forms.html">Draft an offer</a><a class="button secondary" href="governance.html">Read governance</a></div>
</div>
</div>
</section>
<section class="section" aria-labelledby="before-the-gate-before-the-loss">
<div class="section-head">
<h2 id="before-the-gate-before-the-loss">Before the gate, before the loss.</h2>
<p class="body-copy">The strongest first model is a lawful pre-tip or partner-approved handover loop where people can offer useful items before disposal, then explore what belongs in repair, parts, material stock, bench learning, specialist processing or a later decision.</p>
</div>
<div class="grid four"><article class="route-card"><span data-icon="handover"></span><h3>Offer point</h3><p>A public form, collection day, business pickup or supervised drop-off could capture items before they enter the waste stream.</p></article>
<article class="route-card"><span data-icon="bench"></span><h3>Triage bench</h3><p>The first check could ask what the item is, what it can teach, who owns the data, what energy or chemistry it holds, and what skills are needed.</p></article>
<article class="route-card"><span data-icon="lock"></span><h3>Secure storage</h3><p>Lockable containers, cages and sign-out rules can turn curiosity into consentful access instead of chaotic rummaging.</p></article>
<article class="route-card"><span data-icon="ledger"></span><h3>Outcome log</h3><p>Every item can leave a small record: repaired, reused, studied, parts recovered, material tested, returned, processed or paused for deeper review.</p></article></div>
</section>
<div class="band">
<section class="section split " aria-labelledby="trust-comes-from-understanding">
<div>
<h2 id="trust-comes-from-understanding">Trust comes from understanding.</h2>
<p class="body-copy">A good loop can be generous without being vague. It can welcome useful offers while giving people the reasons: chemistry, heat, stored energy, personal data, access rights, contamination, road movement, tool skill and local authority.</p><p class="body-copy">That turns caution into literacy. People can make better sovereign choices when they can see the reason behind the pause, the pathway or the invitation.</p>
</div>
<div class="callout">
<h3>Working boundary</h3>
<p>The exploration starts from consentful handover, clear stewardship, owner-controlled data choices, battery chemistry literacy and a public record of what people chose to do.</p>
</div>
</section>
</div>
<div class="band-sand">
<section class="section" aria-labelledby="a-first-operating-sketch">
<div class="section-head">
<h2 id="a-first-operating-sketch">A first operating sketch.</h2>
<p class="body-copy">This page keeps the operating model plain. Each piece can be tested separately before anyone tries to scale it.</p>
</div>
<div class="flow"><div class="flow-step"><strong>1</strong><p><b>Public offer.</b> A person records an item, stream or repair candidate through the builder or a stewarded intake day.</p></div><div class="flow-step"><strong>2</strong><p><b>Human read.</b> A reviewer and owner look at permission, location, handling, data sovereignty, stored energy, chemistry and available space.</p></div><div class="flow-step"><strong>3</strong><p><b>Pathway choice.</b> The item is marked repair, reuse, parts, material stock, battery learning, chip learning, partner processing, normal disposal or pause-for-research.</p></div><div class="flow-step"><strong>4</strong><p><b>Local work.</b> Suitable items become workshops, repair nights, student projects, microfactory tests or community-use gear.</p></div><div class="flow-step"><strong>5</strong><p><b>Evidence return.</b> The outcome returns to the public record so the next funding or Council conversation has proof.</p></div></div>
</section>
</div>
<section class="section" aria-labelledby="questions-that-could-remove-friction">
<div class="section-head">
<h2 id="questions-that-could-remove-friction">Questions that could remove friction.</h2>
<p class="body-copy">The point of careful questioning is not to shrink the idea. It is to make the first yes easier for people who carry responsibility and for people who want to learn why the risk exists.</p>
</div>
<div class="grid four"><article class="info-card"><h3>Site and traffic</h3><p>Where could vehicles stop, unload and turn around without mixing public curiosity with waste-centre traffic?</p></article>
<a class="info-card" href="https://auraofintelligence.github.io/moreton-bay-community-wealth-and-mutuals/"><h3>Insurance</h3><p>What inductions, supervision, age ranges, tool boundaries, prevention work and mutual-care models would make the risk legible?</p><span class="card-link">Open mutual care index</span></a>
<article class="info-card"><h3>Waste operator role</h3><p>Could the operator flag recoverable items only inside an authorised process, not through informal taking?</p></article>
<article class="info-card"><h3>Council role</h3><p>Could Council support a small evidence pilot without promising a permanent service?</p></article>
<article class="info-card"><h3>Data sovereignty</h3><p>How can owners choose repair, wipe, harvest, archive or destroy pathways without surrendering right-to-repair value?</p></article>
<article class="info-card"><h3>Battery literacy</h3><p>How can lithium, swollen, unknown and damaged packs teach chemistry, fire behaviour, energy storage and careful stewardship?</p></article>
<article class="info-card"><h3>First Nations protocol</h3><p>What local protocol, place naming, cultural respect and land-use care needs to shape the conversation?</p></article>
<article class="info-card"><h3>Public messaging</h3><p>How can signs and posts invite lawful offers, explain the reasons, and keep curiosity inside consentful pathways?</p></article></div>
</section>
</main>
<footer data-site-footer></footer>
<script>window.StraddieTipLoopPages = [{"id": "home", "label": "Home", "href": "index.html"}, {"id": "streams", "label": "Streams", "href": "streams.html"}, {"id": "loop", "label": "Loop", "href": "loop.html"}, {"id": "microfactory", "label": "Microfactory", "href": "microfactory.html"}, {"id": "governance", "label": "Governance", "href": "governance.html"}, {"id": "ecosystem", "label": "Ecosystem", "href": "ecosystem.html"}, {"id": "forms", "label": "Forms", "href": "forms.html"}, {"id": "sources", "label": "Sources", "href": "sources.html"}];</script>
<script src="script.js"></script>
</body>
</html>