-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpartner.html
More file actions
428 lines (386 loc) · 17.4 KB
/
Copy pathpartner.html
File metadata and controls
428 lines (386 loc) · 17.4 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
<!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 | Seeking the Right Partner</title>
<style>
:root {
--bg-main: #0b0f13;
--bg-card: rgba(18, 24, 30, 0.9);
--bg-card-strong: #121a20;
--border-color: rgba(125, 211, 252, 0.18);
--text-primary: #edf6fb;
--text-muted: #9bb0bb;
--accent: #7dd3fc;
--accent-warm: #fbbf24;
--accent-soft: #34d399;
--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(125, 211, 252, 0.14), transparent 34%),
radial-gradient(circle at top right, rgba(251, 191, 36, 0.09), transparent 28%),
linear-gradient(180deg, #0b0f13 0%, #111820 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(125, 211, 252, 0.035) 1px, transparent 1px),
linear-gradient(90deg, rgba(125, 211, 252, 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(11, 15, 19, 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,
.fit-card,
.pilot-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: 54rem;
color: var(--text-primary);
margin-bottom: 1rem;
}
.intro {
max-width: 58rem;
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;
}
.cta.primary {
color: #071117;
background: var(--accent);
border-color: rgba(125, 211, 252, 0.35);
}
.cta.primary:hover {
color: #071117;
text-decoration: none;
background: #a4e3ff;
}
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(125, 211, 252, 0.1);
color: var(--accent);
border: 1px solid rgba(125, 211, 252, 0.24);
}
.panel { padding: 1.5rem; }
.fit-grid,
.pilot-grid,
.proof-grid,
.cta-grid,
.contact-grid {
display: grid;
gap: 1rem;
}
.fit-grid { grid-template-columns: repeat(3, minmax(0, 1fr)); }
.pilot-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
.proof-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
.cta-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
.contact-grid { grid-template-columns: repeat(3, minmax(0, 1fr)); }
.fit-card,
.pilot-card,
.proof-card,
.cta-card,
.contact-card { padding: 1.2rem; }
.fit-card h3,
.pilot-card h3,
.proof-card h3,
.cta-card h3,
.contact-card h3 {
font-family: var(--font-mono);
font-size: 0.98rem;
color: var(--accent);
margin-bottom: 0.5rem;
}
.fit-card p,
.pilot-card p,
.proof-card p,
.cta-card p,
.contact-card p,
.panel p,
li { color: var(--text-muted); }
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) {
.fit-grid,
.pilot-grid,
.proof-grid,
.cta-grid,
.contact-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, .fit-card, .pilot-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="hawk.html">Hawk</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="sweep.html">SWEEP</a>
<a href="case.html">CASE</a>
<a href="improvements.html">Improvements</a>
</div>
</nav>
<header>
<span class="eyebrow">Seeking the Right Partner</span>
<h1>/partner</h1>
<p class="lead">I am looking for the right partner: an owner, founder, or visionary who already knows their best people are burning too much attention on invisible friction.</p>
<p class="intro">This is not a dashboard pitch. It is not generic AI excitement. It is a founder-level proposition: if your team has strong operators but the environment around them is messy, brittle, repetitive, or memory-heavy, then the environment is the bottleneck. That bottleneck can be designed out.</p>
<div class="header-actions">
<a href="#fit" class="cta primary">Who This Is For</a>
<a href="#pilot" class="cta">What A Pilot Looks Like</a>
<a href="#proof" class="cta">Why Believe It</a>
</div>
</header>
<section id="fit">
<h2 class="section-heading">Who This Is For <span class="badge">Partner Fit</span></h2>
<div class="fit-grid">
<article class="fit-card">
<h3>Owners With Operational Sprawl</h3>
<p>Your team gets real work done, but too much of the process still depends on memory, workarounds, path hunting, and manual cleanup that never quite hardens into a system.</p>
</article>
<article class="fit-card">
<h3>Visionaries Who Value Leverage</h3>
<p>You are not looking for noise, gimmicks, or “AI everywhere.” You want a better substrate for execution: less drag, cleaner routine, stronger trust, and more leverage from the same people.</p>
</article>
<article class="fit-card">
<h3>Teams With People Like Me</h3>
<p>Every company has one or two people carrying too much tacit workflow intelligence in their heads. This work is about converting that into infrastructure before it turns into burnout, bottlenecks, or tribal knowledge failure.</p>
</article>
</div>
</section>
<section>
<h2 class="section-heading">What Problem This Solves <span class="badge">Invisible Friction</span></h2>
<div class="panel">
<p>Most companies do not realize how much value they leak through small interruptions: naming cleanup, stale wrappers, scattered files, brittle command habits, unclear routing, folder drift, and tooling that makes smart people do recovery work all day.</p>
<p>Pane, <code>\DOS</code>, Hawk, SWEEP, and the surrounding ecosystem are an attempt to build the opposite: a Windows environment that remembers more, routes better, stays legible, and lowers the invisible maintenance tax on skilled people.</p>
</div>
</section>
<section id="pilot">
<h2 class="section-heading">What A Pilot Looks Like <span class="badge">Practical Start</span></h2>
<div class="pilot-grid">
<article class="pilot-card">
<h3>Start With One Friction Surface</h3>
<p>Pick one high-repeat area: file routing, naming transforms, shell workflows, cleanup logic, or operator-facing Windows structure. Start where people feel the drag every day.</p>
</article>
<article class="pilot-card">
<h3>Build A Trusted Layer</h3>
<p>Implement a governed, logged, human-readable improvement that people can actually feel. No black box. No theater. No broad rollout before trust exists.</p>
</article>
<article class="pilot-card">
<h3>Prove Cognitive Relief</h3>
<p>The point is not only technical correctness. The point is that operators stop paying the same tiny cost over and over, and that reclaimed attention starts showing up in throughput, clarity, and fewer self-inflicted delays.</p>
</article>
<article class="pilot-card">
<h3>Expand Only If It Earns The Right</h3>
<p>Once one surface proves itself, extend into adjacent workflow layers. Grow it because it earned the right, not because it makes for a better feature list.</p>
</article>
</div>
</section>
<section id="proof">
<h2 class="section-heading">Why Believe This <span class="badge">Proof Surfaces</span></h2>
<div class="proof-grid">
<article class="proof-card">
<h3>CASE Shows The Pattern</h3>
<p>Tiny naming transforms can save real cognitive energy because they remove repeated manual recovery. It is a small proof, but that is exactly why it lands fast.</p>
</article>
<article class="proof-card">
<h3>Hawk Shows The Interface</h3>
<p>A predictive, reactive context menu surface shows how the desktop itself can become more aligned with intent instead of making every action harder to reach.</p>
</article>
<article class="proof-card">
<h3>SWEEP Shows Governance</h3>
<p>Cleanup, routing, and metadata can become safer and more legible when the system proposes before it applies and preserves before it deletes.</p>
</article>
<article class="proof-card">
<h3>\DOS Shows Structure</h3>
<p>The root environment can become architectural instead of noisy. That matters because presentation is not decoration. It changes how people think inside the machine.</p>
</article>
</div>
</section>
<section>
<h2 class="section-heading">What I Am Looking For <span class="badge">Right Partner</span></h2>
<div class="panel">
<ul>
<li>An owner or visionary who sees operational drag as a design problem, not just a people problem.</li>
<li>A team with strong operators who would immediately benefit from a better Windows workbench around them.</li>
<li>A partner who values clarity, trust, and infrastructure depth over trend-chasing.</li>
<li>A collaboration that can turn these ideas into a real pilot, real results, and eventually a product or platform.</li>
</ul>
</div>
</section>
<section>
<h2 class="section-heading">Simple Close <span class="badge">Partnership Thesis</span></h2>
<div class="panel">
<p>If your company has people who move faster than the environment around them, then the environment is the bottleneck. That is the bottleneck I want to help fix.</p>
<p>The right partner is not just buying software. They are helping shape a better operating layer for Windows work: one that lowers drag, preserves trust, and gives strong people a cleaner place to do strong work.</p>
</div>
</section>
<section>
<h2 class="section-heading">What I Want Next <span class="badge">Conversation Start</span></h2>
<div class="cta-grid">
<article class="cta-card">
<h3>A Real Pilot Surface</h3>
<p>One team, one workflow, one friction-heavy surface where better structure, routing, naming, or shell behavior can be tested without theatrics.</p>
</article>
<article class="cta-card">
<h3>A Serious Partner Conversation</h3>
<p>The right partner sees this as the beginning of a product or platform relationship, not a one-off tweak. First prove the thesis. Then grow it deliberately.</p>
</article>
</div>
</section>
<section>
<h2 class="section-heading">Who Should Contact Me <span class="badge">Best Fit</span></h2>
<div class="contact-grid">
<article class="contact-card">
<h3>Owners Who Feel The Drag</h3>
<p>You can already feel that your company is paying a tax on invisible friction, scattered routines, and repeated operator recovery work, and you want a sharper operating environment.</p>
</article>
<article class="contact-card">
<h3>Visionaries With A Pilot In Mind</h3>
<p>You have one workflow, one team, or one friction-heavy surface where a better Windows workbench could be tested seriously and measured honestly.</p>
</article>
<article class="contact-card">
<h3>Builders Who Want A Real Partnership</h3>
<p>You are interested in shaping a product or platform relationship around anti-friction infrastructure, not just buying another isolated utility.</p>
</article>
</div>
</section>
<section>
<h2 class="section-heading">Good Next Step <span class="badge">Simple Start</span></h2>
<div class="panel">
<p>The best next conversation is simple: identify one repeated friction surface, describe who feels it most, and decide whether it is worth piloting a better operating layer around that problem.</p>
<p>If that conversation feels obvious, then the fit is probably real.</p>
</div>
</section>
<footer>
<p>© 2026 H.I. Technologies. Build a better environment for the people already carrying the work.</p>
</footer>
</div>
</body>
</html>