-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathsweep.html
More file actions
523 lines (506 loc) · 22.6 KB
/
Copy pathsweep.html
File metadata and controls
523 lines (506 loc) · 22.6 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
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>H.I. Technologies | Why SWEEP Matters</title>
<style>
:root {
--bg-main: #0c120f;
--bg-card: rgba(19, 28, 22, 0.9);
--bg-card-strong: #152019;
--border-color: rgba(134, 239, 172, 0.18);
--text-primary: #eefcf1;
--text-muted: #9eb5a2;
--accent: #86efac;
--accent-warm: #fbbf24;
--accent-soft: #93c5fd;
--accent-alert: #fca5a5;
--shadow: 0 24px 60px rgba(0, 0, 0, 0.32);
--font-sans: "Segoe UI Variable Text", "Trebuchet MS", "Segoe UI", sans-serif;
--font-mono: "Cascadia Code", "Consolas", "Fira Code", monospace;
}
* { box-sizing: border-box; margin: 0; padding: 0; }
html { scroll-behavior: smooth; }
body {
background:
radial-gradient(circle at top left, rgba(134, 239, 172, 0.14), transparent 34%),
radial-gradient(circle at top right, rgba(251, 191, 36, 0.08), transparent 28%),
linear-gradient(180deg, #0c120f 0%, #101913 100%);
color: var(--text-primary);
font-family: var(--font-sans);
line-height: 1.65;
padding: 2rem 1rem 3rem;
min-height: 100vh;
}
body::before {
content: "";
position: fixed;
inset: 0;
pointer-events: none;
background-image:
linear-gradient(rgba(134, 239, 172, 0.035) 1px, transparent 1px),
linear-gradient(90deg, rgba(134, 239, 172, 0.035) 1px, transparent 1px);
background-size: 32px 32px;
mask-image: linear-gradient(180deg, rgba(0, 0, 0, 0.9), transparent);
}
.container { max-width: 1040px; margin: 0 auto; }
.topbar {
position: sticky;
top: 1rem;
z-index: 10;
display: flex;
justify-content: space-between;
align-items: center;
gap: 1rem;
margin-bottom: 1.25rem;
padding: 0.9rem 1rem;
border: 1px solid var(--border-color);
border-radius: 999px;
background: rgba(12, 18, 15, 0.84);
box-shadow: var(--shadow);
backdrop-filter: blur(14px);
}
.topbar-brand,
.topbar-nav a,
.cta {
font-family: var(--font-mono);
text-decoration: none;
}
.topbar-brand { color: var(--text-primary); font-size: 0.9rem; letter-spacing: 0.08em; text-transform: uppercase; }
.topbar-nav { display: flex; flex-wrap: wrap; gap: 0.65rem; }
.topbar-nav a {
color: var(--text-muted);
padding: 0.32rem 0.65rem;
border-radius: 999px;
border: 1px solid transparent;
font-size: 0.92rem;
}
.topbar-nav a:hover,
.cta:hover { color: var(--text-primary); text-decoration: underline; }
header,
.panel,
.model-card,
.strength-card,
.weakness-card,
.future-card,
.proof-card {
border: 1px solid var(--border-color);
background: var(--bg-card);
border-radius: 18px;
box-shadow: var(--shadow);
backdrop-filter: blur(10px);
}
header { padding: 2.45rem; margin-bottom: 2rem; }
.eyebrow {
display: inline-block;
font-family: var(--font-mono);
font-size: 0.78rem;
text-transform: uppercase;
letter-spacing: 0.15em;
color: var(--accent-warm);
margin-bottom: 0.9rem;
}
h1 {
font-size: clamp(2.5rem, 5vw, 4.2rem);
line-height: 1;
letter-spacing: -0.06em;
margin-bottom: 0.95rem;
}
.lead {
font-size: 1.14rem;
max-width: 56rem;
color: var(--text-primary);
margin-bottom: 1rem;
}
.intro {
max-width: 60rem;
color: var(--text-muted);
}
.header-actions {
display: flex;
flex-wrap: wrap;
gap: 0.8rem;
margin-top: 1.4rem;
}
.cta {
display: inline-flex;
align-items: center;
justify-content: center;
padding: 0.82rem 1rem;
border-radius: 999px;
border: 1px solid var(--border-color);
color: var(--accent);
font-size: 0.86rem;
}
section { margin-bottom: 2rem; }
.section-heading {
display: flex;
align-items: center;
gap: 0.7rem;
font-size: 1.35rem;
margin-bottom: 1rem;
}
.badge {
font-family: var(--font-mono);
font-size: 0.75rem;
padding: 0.22rem 0.55rem;
border-radius: 999px;
background: rgba(134, 239, 172, 0.1);
color: var(--accent);
border: 1px solid rgba(134, 239, 172, 0.24);
}
.panel { padding: 1.5rem; }
.model-grid,
.example-grid,
.strength-grid,
.weakness-grid,
.future-grid,
.proof-grid {
display: grid;
gap: 1rem;
}
.model-grid { grid-template-columns: repeat(3, minmax(0, 1fr)); }
.example-grid { grid-template-columns: 1.2fr 0.8fr; }
.strength-grid { grid-template-columns: repeat(3, minmax(0, 1fr)); }
.weakness-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
.future-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
.proof-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
.model-card,
.example-card,
.strength-card,
.weakness-card,
.future-card,
.proof-card { padding: 1.2rem; }
.model-card h3,
.example-card h3,
.strength-card h3,
.weakness-card h3,
.future-card h3,
.proof-card h3 {
font-family: var(--font-mono);
font-size: 0.98rem;
color: var(--accent);
margin-bottom: 0.5rem;
}
.weakness-card h3 { color: var(--accent-alert); }
.future-card h3 { color: var(--accent-soft); }
.model-card p,
.example-card p,
.strength-card p,
.weakness-card p,
.future-card p,
.proof-card p,
.panel p,
li { color: var(--text-muted); }
.example-card {
border: 1px solid var(--border-color);
background: var(--bg-card);
border-radius: 18px;
box-shadow: var(--shadow);
backdrop-filter: blur(10px);
}
.example-card pre {
margin-top: 0.85rem;
padding: 1rem;
border-radius: 14px;
border: 1px solid rgba(134, 239, 172, 0.14);
background: rgba(8, 13, 10, 0.88);
color: var(--text-primary);
font-family: var(--font-mono);
font-size: 0.83rem;
line-height: 1.55;
overflow-x: auto;
}
.example-meta {
list-style: none;
padding-left: 0;
margin-top: 0.85rem;
}
.example-meta li {
padding: 0.7rem 0;
border-bottom: 1px solid rgba(134, 239, 172, 0.12);
}
.example-meta li:last-child {
border-bottom: 0;
padding-bottom: 0;
}
.refs-list {
list-style: none;
padding-left: 0;
}
.refs-list li {
padding: 0.9rem 0;
border-bottom: 1px solid rgba(134, 239, 172, 0.12);
}
.refs-list li:last-child {
border-bottom: 0;
padding-bottom: 0;
}
ul {
padding-left: 1.1rem;
display: grid;
gap: 0.45rem;
}
code { font-family: var(--font-mono); color: var(--text-primary); }
footer {
margin-top: 4rem;
border-top: 1px solid var(--border-color);
padding-top: 1.4rem;
text-align: center;
font-size: 0.85rem;
color: var(--text-muted);
font-family: var(--font-mono);
}
@media (max-width: 900px) {
.model-grid,
.example-grid,
.strength-grid,
.weakness-grid,
.future-grid,
.proof-grid { grid-template-columns: 1fr; }
}
@media (max-width: 640px) {
body { padding: 1rem 0.85rem 2.5rem; }
.topbar { position: static; border-radius: 18px; flex-direction: column; align-items: flex-start; }
header, .panel, .model-card, .strength-card, .weakness-card, .future-card, .proof-card { border-radius: 14px; }
header { padding: 1.45rem; }
.header-actions { flex-direction: column; align-items: stretch; }
}
</style>
</head>
<body>
<div class="container">
<nav class="topbar" aria-label="Primary">
<a href="index.html" class="topbar-brand">H.I. Technologies</a>
<div class="topbar-nav">
<a href="index.html">Home</a>
<a href="partner.html">Partner</a>
<a href="mcp.html">MCP</a>
<a href="governance.html">Governance</a>
<a href="compiler.html">COMPILER</a>
<a href="git.html">Git</a>
<a href="improvements.html">Improvements</a>
</div>
</nav>
<header>
<span class="eyebrow">Preserve-First File Janitor</span>
<h1>/sweep</h1>
<p class="lead">SWEEP matters because clutter is not just ugly. It is cognitive drag. When files pile up in the wrong place, strong people waste attention sorting, deciding, re-deciding, and recovering their own systems by hand.</p>
<p class="intro">SWEEP uses <code>mcp.ini</code> as its rule authority. For now it is silo-based, meaning the parent domain defines what stays and what moves. It can run on a timer, on a schedule, or on demand. It is WAL-ready, low resource, low impact, fully logged, and designed to write later rather than thrash the environment in real time.</p>
<div class="header-actions">
<a href="#model" class="cta">Operating Model</a>
<a href="#example" class="cta">Example Policy</a>
<a href="#strengths" class="cta">Strengths</a>
<a href="#future" class="cta">Future</a>
</div>
</header>
<section id="model">
<h2 class="section-heading">Operating Model <span class="badge">Silo First</span></h2>
<div class="model-grid">
<article class="model-card">
<h3>Silo-Based Rules</h3>
<p>SWEEP operates by parent domain for now. The silo decides what belongs, what stays, and what should move elsewhere. Nothing global yet, because local coherence comes first.</p>
</article>
<article class="model-card">
<h3>Write Later</h3>
<p>The process is deliberately low-impact. It can observe, queue, log, and prepare before acting, which keeps the machine calm instead of thrashing the filesystem constantly.</p>
</article>
<article class="model-card">
<h3>Timer, Schedule, On Demand</h3>
<p>SWEEP can be invoked by clock, by planned schedule, or by explicit operator intent. That flexibility matters because different silos want different rhythms of cleanup.</p>
</article>
</div>
</section>
<section id="example">
<h2 class="section-heading">Example Silo Policy <span class="badge">Concrete Proof</span></h2>
<div class="example-grid">
<article class="example-card">
<h3>Example <code>mcp.ini</code> Rule Set</h3>
<p>This is the kind of rule surface that makes SWEEP useful. It is readable, local to the silo, and easy to audit later.</p>
<pre>[silo:ClipboardExports]
root = C:\DOS\ClipboardExports
mode = wal-ready
schedule = every 20 minutes
on_demand = true
log = C:\DOS\Logs\sweep-clipboardexports.log
[keep]
patterns = *.db;*.sqlite;*.md;*.ps1;*.json
paths = active\;research\;actions\
[move:images]
patterns = *.png;*.jpg;*.webp
target = C:\DOS\ClipboardExports\media\images
[move:archives]
patterns = *.zip;*.7z;*.rar
target = C:\DOS\ClipboardExports\holding\archives
[move:staging]
patterns = *.tmp;*.bak;*.old
target = C:\DOS\ClipboardExports\holding\staging
[safety]
dry_run_first = true
preserve_original_timestamps = true
conflict_mode = suffix
delete_source = false</pre>
</article>
<article class="example-card">
<h3>What Happens</h3>
<p>SWEEP reads the silo rule file, evaluates the current folder state, records intent, and then processes according to the selected rhythm.</p>
<ul class="example-meta">
<li><strong>Timer:</strong> A light recurring pass keeps the silo from accumulating obvious clutter.</li>
<li><strong>Schedule:</strong> Heavier movement can wait for off-hours or the quiet part of the day.</li>
<li><strong>On Demand:</strong> An operator can run SWEEP before a handoff, export, backup, or review.</li>
<li><strong>WAL-Ready:</strong> The engine can observe and queue first, then write after confidence is high enough.</li>
</ul>
<pre>2026-06-01T09:20:00Z SWEEP silo=ClipboardExports mode=dry-run
2026-06-01T09:20:00Z KEEP notes\session-map.md
2026-06-01T09:20:00Z MOVE dump\capture-4419.png -> media\images\capture-4419.png
2026-06-01T09:20:01Z MOVE inbox\old-bundle.zip -> holding\archives\old-bundle.zip
2026-06-01T09:20:01Z HOLD inbox\active-plan.md reason=keep-pattern
2026-06-01T09:20:01Z DONE scanned=148 moved=2 held=1 skipped=145</pre>
</article>
</div>
</section>
<section>
<h2 class="section-heading">Why This Starts Silo-First <span class="badge">Control First</span></h2>
<div class="panel">
<p>Silo-first keeps SWEEP accountable. A parent domain can define policy, test behavior, and audit movement without risking cross-environment spillover.</p>
<p>This reduces blast radius, preserves local intent, and builds trust faster. Once a silo proves stable under real work, the same pattern can scale into broader orchestration.</p>
</div>
</section>
<section id="strengths">
<h2 class="section-heading">Strengths <span class="badge">What It Does Well</span></h2>
<div class="strength-grid">
<article class="strength-card">
<h3>Low Resource, Low Impact</h3>
<p>SWEEP is built to stay out of the way. It should not become the new source of drag while trying to solve drag.</p>
</article>
<article class="strength-card">
<h3>Fully Logged</h3>
<p>Every move, copy, skip, conflict, and fallback can be logged. That matters because trust requires visibility.</p>
</article>
<article class="strength-card">
<h3>Preserve First</h3>
<p>The design defaults toward preservation instead of hard deletion. That is safer for both operations and human confidence.</p>
</article>
<article class="strength-card">
<h3>MCP-Backed Rules</h3>
<p><code>mcp.ini</code> gives SWEEP a readable rule authority so cleanup logic does not disappear into a tangle of one-off scripts.</p>
</article>
<article class="strength-card">
<h3>WAL-Ready Direction</h3>
<p>The write-later model points toward safer transactional behavior: observation first, recorded intent second, execution after confidence.</p>
</article>
<article class="strength-card">
<h3>Operator Relief</h3>
<p>The real strength is not file movement by itself. It is removing repeated classification and cleanup decisions from the operator’s head.</p>
</article>
</div>
</section>
<section>
<h2 class="section-heading">Weaknesses It Overcomes <span class="badge">What It Replaces</span></h2>
<div class="weakness-grid">
<article class="weakness-card">
<h3>Extraneous Cognitive Load</h3>
<p>Unorganized folders force people to spend working memory on navigation and cleanup instead of the actual task. SWEEP reduces that waste by handling structure consistently.</p>
</article>
<article class="weakness-card">
<h3>Decision Fatigue</h3>
<p>Deciding where each file should go is a low-value internal burden. Offloading that burden to a governed framework preserves attention for higher-value thinking.</p>
</article>
<article class="weakness-card">
<h3>Metacognitive Drag</h3>
<p>People should not have to keep re-managing their own environment all day. SWEEP reduces the recurring tax of monitoring, sorting, and reclassifying information.</p>
</article>
<article class="weakness-card">
<h3>Context Switching</h3>
<p>Every cleanup interruption leaves residue. If the system can keep folders coherent in the background or on demand, people spend less time rebuilding focus.</p>
</article>
</div>
</section>
<section>
<h2 class="section-heading">Why A Founder Cares <span class="badge">Strategic Value</span></h2>
<div class="panel">
<p>Founders usually do not lose money because a folder is messy once. They lose money because the same small mess keeps forcing smart people to stop, sort, remember, decide, and recover their place.</p>
<p>SWEEP matters because it converts that hidden tax into governed infrastructure. It gives a team a cleaner environment without asking them to become their own file janitors forever.</p>
</div>
</section>
<section>
<h2 class="section-heading">Research Support <span class="badge">Human Factors</span></h2>
<div class="proof-grid">
<article class="proof-card">
<h3>Cognitive Load</h3>
<p>Cognitive Load Theory supports the idea that cluttered, poorly structured digital spaces impose extraneous load that does not help the real task and can instead exhaust working memory.</p>
</article>
<article class="proof-card">
<h3>Cognitive Offloading</h3>
<p>Cognitive offloading research supports delegating low-value classification work to external tools so finite neural resources can stay focused on high-value tasks.</p>
</article>
<article class="proof-card">
<h3>Metacognitive Overhead</h3>
<p>Kirsh’s work supports the claim that people suffer when they must continually manage desks, files, projects, and their own information structure manually.</p>
</article>
<article class="proof-card">
<h3>Interruption Cost</h3>
<p>Research on workplace interruptions supports the idea that even small cleanup breaks can leave attention residue and extend recovery time after focus is broken.</p>
</article>
</div>
</section>
<section id="future">
<h2 class="section-heading">Future Direction <span class="badge">Kernel Path</span></h2>
<div class="future-grid">
<article class="future-card">
<h3>Beyond The Silo</h3>
<p>Today the rules are local to the parent domain. Later, SWEEP could coordinate across silos without losing the safety of local authority.</p>
</article>
<article class="future-card">
<h3>Stronger WAL Behavior</h3>
<p>The write-later model can mature into a fuller transactional path: observed intent, staged record, then action with clear rollback and audit semantics.</p>
</article>
<article class="future-card">
<h3>Evidence-Driven Promotion</h3>
<p>Repeated file patterns could propose new rules into <code>mcp.ini</code> for review, so SWEEP becomes more intelligent without becoming self-authorizing.</p>
</article>
<article class="future-card">
<h3>Background Trust Layer</h3>
<p>The long-term opportunity is a background file-governance layer that stays quiet, low-impact, and explainable while reducing operational noise for the whole team.</p>
</article>
</div>
</section>
<section>
<h2 class="section-heading">References <span class="badge">Support</span></h2>
<div class="panel">
<ul class="refs-list">
<li>
<strong>Kirsh, D. (2000).</strong> <em>A Few Thoughts on Cognitive Overload.</em> Intellectica.
<br>
<code>https://doi.org/10.3406/intel.2000.1592</code>
</li>
<li>
<strong>Mark, G., Czerwinski, M., & Iqbal, S. T. (2018).</strong> <em>Effects of Individual Differences in Blocking Workplace Distractions.</em> CHI.
<br>
<code>https://doi.org/10.1145/3173574.3173666</code>
</li>
<li>
<strong>Risko, E. F., & Gilbert, S. J. (2016).</strong> <em>Cognitive Offloading.</em> Trends in Cognitive Sciences.
</li>
<li>
<strong>Sigolo, B. O. O. (n.d.).</strong> <em>Contributions of cognitive load theory to understanding information overload.</em>
</li>
<li>
<strong>Jose, B. (2025).</strong> <em>The cognitive paradox of AI in education: between enhancement and erosion.</em> Frontiers in Psychology.
</li>
<li>
<strong>Peng, J. L. (n.d.).</strong> <em>Cognitive Offloading in Short-Term Memory Tasks: Trust Toward Tools as a Moderator.</em>
</li>
<li>
<strong>Tip, P. (n.d.).</strong> <em>Focus Recovery After Interruptions: 3-Phase Protocol.</em>
</li>
</ul>
</div>
</section>
<footer>
<p>© 2026 H.I. Technologies. A cleaner environment is not cosmetic when it gives a team its attention back.</p>
</footer>
</div>
</body>
</html>