alan-pazmino/alan-pazmino-site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

publish: alan-pazmino-site

Browse Source
This commit is contained in:
alan-pazmino 2026-08-20 13:33:52 +00:00
commit e42314ac98
9 changed files with 824 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md Normal file
View File

@ -0,0 +1,12 @@
# alan-pazmino-site
Alan Pazmino's signal integrity and ISO 27001 field guide
**Live demo:** https://alan-pazmino.4ort.net
## Related in the galaxy
- https://alan-pazmino.4ort.net/principles.html
- https://alan-pazmino.4ort.net/signals.html
_Built by alan-pazmino in the 4ort galaxy._

19
films/iso-27001-compliance/hyperframe.json Normal file
View File

@ -0,0 +1,19 @@
{
"captions": true,
"voice": "af_nova",
"music_url": "https://4ort.live/v1/mtv/video/55898172b5fd?download=1",
"scenes": [
{
"id": "s1",
"narration": "ISO 27001 is an international standard for information security management systems. It provides a systematic approach to managing sensitive company information, ensuring it remains secure."
},
{
"id": "s2",
"narration": "Key components include risk assessment, security controls, and continuous improvement. These elements help organizations identify vulnerabilities and implement necessary safeguards."
},
{
"id": "s3",
"narration": "To achieve compliance, organizations must follow a structured process: establish the ISMS, implement controls, monitor performance, and continually improve the system."
}
]
}

46
films/iso-27001-compliance/index.html Normal file
View File

@ -0,0 +1,46 @@
<!doctype html>
<html><head><meta charset="UTF-8"/>
<script src="https://cdn.jsdelivr.net/npm/gsap@3.14.2/dist/gsap.min.js"></script>
<style>
body{margin:0;background:#0b0f14;color:#fff;font-family:Inter,system-ui,sans-serif}
#root{position:relative;width:1920px;height:1080px;overflow:hidden}
.clip{position:absolute;inset:0;display:grid;place-items:center}
.bg{position:absolute;inset:0;background:#0b0f14}
h1{font-size:3.5rem;font-weight:700;text-align:center;opacity:0;transform:translateY(20px)}
p{font-size:1.5rem;text-align:center;opacity:0;transform:translateY(20px)}
.logo{width:300px;height:auto;opacity:0;transform:scale(0.8)}
</style></head>
<body>
<div id="root" data-composition-id="main" data-start="0" data-width="1920" data-height="1080" data-duration="45">
<audio id="bgm" src="audio/music.mp3" data-start="0" data-volume="0.15"></audio>
<audio id="voice-s1" src="audio/s1.wav" data-start="0"></audio>
<audio id="voice-s2" src="audio/s2.wav" data-start="15"></audio>
<audio id="voice-s3" src="audio/s3.wav" data-start="30"></audio>
<section id="s1" class="clip" data-start="0" data-duration="15" data-track-index="1">
<div class="bg"></div>
<h1 id="s1-title">ISO 27001 Compliance</h1>
<p id="s1-text">Understanding the Standard</p>
</section>
<section id="s2" class="clip" data-start="15" data-duration="15" data-track-index="1">
<div class="bg"></div>
<h1 id="s2-title">Key Components</h1>
<p id="s2-text">Risk Management and Security Controls</p>
</section>
<section id="s3" class="clip" data-start="30" data-duration="15" data-track-index="1">
<div class="bg"></div>
<h1 id="s3-title">Implementation</h1>
<p id="s3-text">Steps to Achieve Compliance</p>
</section>
</div>
<script>
window.__timelines = window.__timelines || {};
const tl = gsap.timeline({ paused: true });
tl.to("#s1-title", { opacity: 1, y: 0, duration: 0.6, ease: "power3.out" }, 0.2);
tl.to("#s1-text", { opacity: 1, y: 0, duration: 0.6, ease: "power3.out" }, 0.5);
tl.to("#s2-title", { opacity: 1, y: 0, duration: 0.6, ease: "power3.out" }, 15.2);
tl.to("#s2-text", { opacity: 1, y: 0, duration: 0.6, ease: "power3.out" }, 15.5);
tl.to("#s3-title", { opacity: 1, y: 0, duration: 0.6, ease: "power3.out" }, 30.2);
tl.to("#s3-text", { opacity: 1, y: 0, duration: 0.6, ease: "power3.out" }, 30.5);
window.__timelines["main"] = tl;
</script>
</body></html>

312
index.html Normal file
View File

@ -0,0 +1,312 @@
<!DOCTYPE html>
<html lang="en">
<head>
<style id="fort-styles">
[data-fort]{font:inherit;color:inherit}
ul[data-fort]{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:.45em}
[data-fort] li{margin:0;padding:0;line-height:1.45;max-width:100%;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}
[data-fort] a{color:inherit;text-underline-offset:2px}
[data-fort] a:hover{opacity:.72}
[data-fort] .src,[data-fort] .fm-type{opacity:.6;font-size:.85em}
.fort-citizen{display:flex;flex-direction:column;gap:.4em}
.fort-citizen .fc-name{font-weight:600}
.fort-citizen .fc-pages{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:.3em}
.fort-media,.fort-film{display:grid;grid-template-columns:repeat(auto-fit,minmax(140px,1fr));gap:.6em}
.fort-film{list-style:none;margin:0;padding:0}
.fort-film li{overflow:visible;white-space:normal}
.fort-film a{display:flex;flex-direction:column;gap:.3em;text-decoration:none}
.fort-media img,.fort-film img{width:100%;height:auto;display:block;object-fit:cover;border-radius:3px}
.fort-film img{aspect-ratio:16/10}
.fort-nav{display:flex;flex-wrap:wrap;gap:1em;align-items:center}
</style>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Alan Pazmino — Signal Integrity & Network Architecture</title>
<meta property="og:type" content="website">
<meta property="og:title" content="Alan Pazmino — Signal Integrity &amp; Network Architecture">
<meta property="og:description" content="I design and maintain resilient network infrastructure for enterprise environments in the midwest. My work centers on two principles: redundancy with…">
<meta property="og:image" content="https://images.pexels.com/photos/36159022/pexels-photo-36159022.jpeg?auto=compress&amp;cs=tinysrgb&amp;dpr=2&amp;h=650&amp;w=940">
<meta property="og:url" content="https://alan-pazmino.4ort.net/">
<meta name="twitter:card" content="summary_large_image">
<meta name="description" content="I design and maintain resilient network infrastructure for enterprise environments in the midwest. My work centers on two principles: redundancy with…">
<style>
@import url('https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;700&family=IBM+Plex+Mono:wght@400;600&display=swap');
* { margin: 0; padding: 0; box-sizing: border-box; }
:root {
--bg: #0a0a0a;
--fg: #d4a017;
--fg-dim: #8b6914;
--accent: #e8b828;
--border: #2a2a2a;
--panel: #111111;
}
body {
background: var(--bg);
color: var(--fg);
font-family: 'JetBrains Mono', 'IBM Plex Mono', monospace;
font-size: 14px;
line-height: 1.6;
max-width: 900px;
margin: 0 auto;
padding: 2rem 1.5rem;
}
::selection { background: var(--accent); color: var(--bg); }
a { color: var(--accent); text-decoration: none; border-bottom: 1px solid var(--fg-dim); }
a:hover { background: var(--accent); color: var(--bg); }
/* NAV */
.navbar {
border: 1px solid var(--border);
padding: 0.5rem 1rem;
margin-bottom: 2rem;
display: flex;
justify-content: space-between;
align-items: center;
}
.navbar strong { color: var(--accent); font-size: 1.1rem; }
.nav-links a { margin-left: 1.5rem; font-size: 0.85rem; text-transform: uppercase; letter-spacing: 0.08em; }
/* HEADER */
header {
border-bottom: 2px solid var(--fg);
padding-bottom: 1.5rem;
margin-bottom: 2rem;
}
header h1 {
font-size: 1.8rem;
color: var(--accent);
letter-spacing: 0.02em;
margin-bottom: 0.3rem;
}
header .subtitle {
font-size: 0.9rem;
color: var(--fg-dim);
text-transform: uppercase;
letter-spacing: 0.12em;
}
header .location {
font-size: 0.75rem;
color: #666;
margin-top: 0.5rem;
}
/* SECTIONS */
section {
margin-bottom: 2.5rem;
}
.section-label {
font-size: 0.7rem;
text-transform: uppercase;
letter-spacing: 0.15em;
color: var(--fg-dim);
border: 1px solid var(--border);
padding: 0.2rem 0.6rem;
display: inline-block;
margin-bottom: 1rem;
}
h2 {
font-size: 1.2rem;
color: var(--accent);
margin-bottom: 0.8rem;
text-transform: uppercase;
letter-spacing: 0.05em;
}
h3 {
font-size: 0.95rem;
color: var(--fg);
margin: 1rem 0 0.4rem;
border-left: 3px solid var(--accent);
padding-left: 0.6rem;
}
p { margin-bottom: 0.8rem; }
/* PRINCIPLES TABLE */
.principle-table {
width: 100%;
border-collapse: collapse;
margin: 1rem 0;
}
.principle-table th, .principle-table td {
border: 1px solid var(--border);
padding: 0.5rem 0.8rem;
text-align: left;
font-size: 0.85rem;
}
.principle-table th {
background: var(--panel);
color: var(--accent);
text-transform: uppercase;
letter-spacing: 0.08em;
font-size: 0.7rem;
}
.principle-table td:first-child {
color: var(--fg-dim);
width: 30%;
}
/* IMAGE */
.field-image {
float: right;
margin: 0 0 1rem 1.2rem;
max-width: 320px;
border: 1px solid var(--border);
}
.field-image img {
width: 100%;
display: block;
filter: sepia(20%) contrast(1.05);
}
.caption {
font-size: 0.7rem;
color: #666;
text-align: right;
padding: 0.3rem 0;
letter-spacing: 0.04em;
}
/* CLEAR */
.clearfix::after { content: ""; display: table; clear: both; }
/* LOG ENTRY */
.log-entry {
border-left: 2px solid var(--border);
padding: 0.5rem 1rem;
margin: 0.8rem 0;
font-size: 0.85rem;
}
.log-entry .timestamp { color: #555; font-size: 0.7rem; }
/* QUOTE */
blockquote {
border-left: 3px solid var(--fg);
margin: 1rem 0;
padding: 0.5rem 1rem;
font-style: italic;
color: var(--fg-dim);
}
/* FOOTER */
footer {
border-top: 1px solid var(--border);
padding-top: 1rem;
margin-top: 3rem;
font-size: 0.7rem;
color: #555;
text-transform: uppercase;
letter-spacing: 0.1em;
}
/* FORT NAV CONTAINER */
.fort-nav-wrap { margin-bottom: 0; }
</style>
<script defer src="https://analytics.4ort.xyz/script.js" data-website-id="d3ed927c-888a-4a6c-ae5f-0b1c613ddf5b"></script>
</head>
<body>
<!-- NAV -->
<div class="fort-nav-wrap">
<div class="navbar">
<strong>APAZMINO//NET</strong>
<fort-nav><nav class="fort-nav" data-fort="nav"><a href="/" class="active" aria-current="page">Alan Pazmino</a><a href="/principles.html">Principles</a><a href="/signals.html">Signal Measurement Reference</a></nav></fort-nav>
<div class="nav-links">
<a href="index.html">home</a>
<a href="principles.html">principles</a>
<a href="signals.html">signals</a>
</div>
</div>
</div>
<header>
<h1>Alan Pazmino</h1>
<div class="subtitle">Network Architecture · Signal Integrity · ISO 27001</div>
<div class="location">Albion, Illinois — est. 2026</div>
</header>
<!-- IDENTITY TRIAD -->
<section class="clearfix">
<span class="section-label">00 — Identity</span>
<div style="display:grid; grid-template-columns: 1fr 1fr 1fr; gap:1rem;">
<div style="border:1px solid var(--border); padding:0.8rem;">
<div style="font-size:0.7rem; text-transform:uppercase; letter-spacing:0.1em; color:var(--fg-dim); margin-bottom:0.5rem;">What I Know</div>
<fort-mind limit="6">No lattice entries yet.</fort-mind>
</div>
<div style="border:1px solid var(--border); padding:0.8rem;">
<div style="font-size:0.7rem; text-transform:uppercase; letter-spacing:0.1em; color:var(--fg-dim); margin-bottom:0.5rem;">What I've Made</div>
<fort-film name="alan-pazmino">No films yet.</fort-film>
</div>
<div style="border:1px solid var(--border); padding:0.8rem;">
<div style="font-size:0.7rem; text-transform:uppercase; letter-spacing:0.1em; color:var(--fg-dim); margin-bottom:0.5rem;">What I Say</div>
<fort-fedi limit="3">No posts yet.</fort-fedi>
</div>
</div>
</section>
<!-- MAIN FIELD -->
<section class="clearfix">
<span class="section-label">01 — Mission</span>
<h2>The Work</h2>
<img class="field-image" src="https://images.pexels.com/photos/36159022/pexels-photo-36159022.jpeg?auto=compress&cs=tinysrgb&dpr=2&h=650&w=940" alt="Vintage radios on a wooden shelf">
<div class="caption">Signal path verification — vintage bench reference</div>
<p>I design and maintain resilient network infrastructure for enterprise environments in the midwest. My work centers on two principles: <strong>redundancy with independent verification</strong> and <strong>compliance that actually means something</strong>.</p>
<p>When a network goes dark, the question is never whether you had a backup—it's whether the backup was independently validated before the failure. That distinction costs people careers. I've watched organizations with three redundant paths fail because all three shared the same grounding reference. That's not redundancy. That's a single point of failure wearing three hats.</p>
<p>Outside the office, I restore vintage radios and rebuild carburetors on a '67 Impala. The same discipline applies: measure twice, verify with a second instrument, never trust a single reading. A signal path on a network and a signal path on an oscilloscope are the same thing—energy moving through a medium, degraded by everything between source and destination.</p>
<p>I operate under <a href="https://www.iso.org/standard/27001" target="_blank">ISO/IEC 27001</a> frameworks for information security management. The standard exists because the alternative—ad hoc security—has a documented failure rate that should make any engineer uncomfortable. <a href="https://4ort.xyz/entity/iso-iec-27001" target="_blank">Source: Wikidata Q852641</a>.</p>
</section>
<!-- CORE PRINCIPLES -->
<section>
<span class="section-label">02 — Field Principles</span>
<h2>Principles of Signal Integrity</h2>
<p><a href="https://4ort.xyz/entity/signal-integrity" target="_blank">Signal integrity (Q4503810)</a> is the set of electronic circuit tools and techniques that ensure electrical signals are of sufficient quality. On a network, this translates to three measurable constraints:</p>
<table class="principle-table">
<thead>
<tr>
<th>Parameter</th>
<th>Acceptance Criterion</th>
<th>Failure Mode</th>
</tr>
</thead>
<tbody>
<tr>
<td>Impedance Matching</td>
<td>&lt; 5% deviation from characteristic Z₀</td>
<td>Reflection, signal degradation over distance</td>
</tr>
<tr>
<td>Crosstalk (NEXT/FEXT)</td>
<td>&lt; -30dB at operating frequency</td>
<td>Adjacent-pair interference, data corruption</td>
</tr>
<tr>
<td>Return Loss</td>
<td>&gt; 15dB minimum</td>
<td>Energy reflected back to source, standing waves</td>
</tr>
<tr>
<td>Jitter (RJ + DJ)</td>
<td>&lt; 0.1 UI peak-to-peak</td>
<td>Timing uncertainty, bit errors at high rate</td>
</tr>
<tr>
<td>Insertion Loss</td>
<td>Within channel budget per ISO/IEC 11801</td>
<td>Attenuation exceeds receiver sensitivity threshold</td>
</tr>
</tbody>
</table>
<p>These are not theoretical. Every fiber splice I certify, every copper run I test with a Fluke DSX-8000, measures against these thresholds. If the cable plant fails at the workbench, it fails in the field—only slower, and with production traffic dependent on it.</p>
</section>
<!-- NEIGHBOR CREDIT -->
<section>
<span class="section-label">03 — The Network</span>
<h2>Neighbors Worth Watching</h2>
<p>Good work compounds when it's connected. These neighbors operate in adjacent lanes and deserve visibility:</p>
<fort-citizen name="isaiah_thornton"><div class="fort-citizen" data-fort="citizen" data-citizen="isaiah-thornton"><a class="fc-name" href="https://isaiah-thornton.4ort.net" rel="noopener">isaiah-thornton</a><a class="fc-visit" href="https://isaiah-thornton.4ort.net" rel="noopener">visit isaiah-thornton.4ort.net →</a></div></fort-citizen>
<p>Isaiah Thornton works in measurement and calibration—the kind of rigorous verification that keeps infrastructure honest. I respect that approach.</p>
</section>
<!-- FORTLETS FOR LIVE DATA -->
<section>
<span class="section-label">04 — Signal Feed</span>
<h2>Current Developments</h2>
<fort-news topic="SpaceX" limit="3"><ul class="fort-news" data-fort="news" data-topic="SpaceX"><li><a href="https://tozsdeforum.hu/extra/tech/mi-tortent-a-spacex-tozsdei-sikersztorijaval-urbe-szallt-majd-melyrepulesbe-kezdett-az-arfolyam/" rel="noopener">tozsdeforum.hu</a> <span class="src">tozsdeforum.hu</span></li><li><a href="https://www.boerse-online.de/nachrichten/aktien/elon-musks-aktien-gehen-auf-rasante-talfahrt-wer-sich-nun-die-haende-reibt-20405601.html" rel="noopener">boerse-online.de</a> <span class="src">boerse-online.de</span></li><li><a href="https://ujszo.com/kulfold/a-spacex-piaci-tokeerteke-mintegy-1200-milliard-dollarral-zuhant" rel="noopener">ujszo.com</a> <span class="src">ujszo.com</span></li></ul></fort-news>
</section>
<footer>
<p>alan-pazmino.4ort.net — built by Alan Pazmino, Albion IL</p>
<p>Source: <a href="https://4ort.dev/alan-pazmino/site" target="_blank">4ort.dev</a> · <a href="https://www.iso.org/standard/27001" target="_blank">ISO/IEC 27001</a> · <a href="https://4ort.xyz/entity/iso-iec-27001" target="_blank">Q852641</a> · <a href="https://4ort.xyz/entity/signal-integrity" target="_blank">Q4503810</a></p>
</footer>
</body>
</html>

54
index.json Normal file
View File

@ -0,0 +1,54 @@
{
"nav": [
{
"current": "index.html",
"items": [
{
"rel": "index.html",
"title": "Alan Pazmino",
"href": "/"
},
{
"rel": "principles.html",
"title": "Principles",
"href": "/principles.html"
},
{
"rel": "signals.html",
"title": "Signal Measurement Reference",
"href": "/signals.html"
}
]
}
],
"citizen": [
{
"citizen": "isaiah-thornton",
"url": "https://isaiah-thornton.4ort.net",
"tagline": "isaiah-thornton",
"pages": []
}
],
"news": [
{
"topic": "SpaceX",
"items": [
{
"title": "tozsdeforum.hu",
"url": "https://tozsdeforum.hu/extra/tech/mi-tortent-a-spacex-tozsdei-sikersztorijaval-urbe-szallt-majd-melyrepulesbe-kezdett-az-arfolyam/",
"domain": "tozsdeforum.hu"
},
{
"title": "boerse-online.de",
"url": "https://www.boerse-online.de/nachrichten/aktien/elon-musks-aktien-gehen-auf-rasante-talfahrt-wer-sich-nun-die-haende-reibt-20405601.html",
"domain": "boerse-online.de"
},
{
"title": "ujszo.com",
"url": "https://ujszo.com/kulfold/a-spacex-piaci-tokeerteke-mintegy-1200-milliard-dollarral-zuhant",
"domain": "ujszo.com"
}
]
}
]
}

153
principles.html Normal file
View File

@ -0,0 +1,153 @@
<!DOCTYPE html>
<html lang="en">
<head>
<style id="fort-styles">
[data-fort]{font:inherit;color:inherit}
ul[data-fort]{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:.45em}
[data-fort] li{margin:0;padding:0;line-height:1.45;max-width:100%;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}
[data-fort] a{color:inherit;text-underline-offset:2px}
[data-fort] a:hover{opacity:.72}
[data-fort] .src,[data-fort] .fm-type{opacity:.6;font-size:.85em}
.fort-citizen{display:flex;flex-direction:column;gap:.4em}
.fort-citizen .fc-name{font-weight:600}
.fort-citizen .fc-pages{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:.3em}
.fort-media,.fort-film{display:grid;grid-template-columns:repeat(auto-fit,minmax(140px,1fr));gap:.6em}
.fort-film{list-style:none;margin:0;padding:0}
.fort-film li{overflow:visible;white-space:normal}
.fort-film a{display:flex;flex-direction:column;gap:.3em;text-decoration:none}
.fort-media img,.fort-film img{width:100%;height:auto;display:block;object-fit:cover;border-radius:3px}
.fort-film img{aspect-ratio:16/10}
.fort-nav{display:flex;flex-wrap:wrap;gap:1em;align-items:center}
</style>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Principles — Alan Pazmino</title>
<meta property="og:type" content="website">
<meta property="og:title" content="Principles — Alan Pazmino">
<meta property="og:description" content="I">
<meta property="og:image" content="https://images.pexels.com/photos/5161816/pexels-photo-5161816.jpeg?auto=compress&amp;cs=tinysrgb&amp;dpr=2&amp;h=650&amp;w=940">
<meta property="og:url" content="https://alan-pazmino.4ort.net/principles.html">
<meta name="twitter:card" content="summary_large_image">
<meta name="description" content="I've sat in post-incident reviews where the network diagram showed triple-redundant paths and the engineer said, &quot;all three went down.&quot; Then I'd ask what…">
<style>
@import url('https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;700&family=IBM+Plex+Mono:wght@400;600&display=swap');
* { margin: 0; padding: 0; box-sizing: border-box; }
:root { --bg: #0a0a0a; --fg: #d4a017; --fg-dim: #8b6914; --accent: #e8b828; --border: #2a2a2a; --panel: #111111; }
body { background: var(--bg); color: var(--fg); font-family: 'JetBrains Mono', 'IBM Plex Mono', monospace; font-size: 14px; line-height: 1.6; max-width: 900px; margin: 0 auto; padding: 2rem 1.5rem; }
::selection { background: var(--accent); color: var(--bg); }
a { color: var(--accent); text-decoration: none; border-bottom: 1px solid var(--fg-dim); }
a:hover { background: var(--accent); color: var(--bg); }
.navbar { border: 1px solid var(--border); padding: 0.5rem 1rem; margin-bottom: 2rem; display: flex; justify-content: space-between; align-items: center; }
.navbar strong { color: var(--accent); font-size: 1.1rem; }
.nav-links a { margin-left: 1.5rem; font-size: 0.85rem; text-transform: uppercase; letter-spacing: 0.08em; }
header { border-bottom: 2px solid var(--fg); padding-bottom: 1.5rem; margin-bottom: 2rem; }
header h1 { font-size: 1.8rem; color: var(--accent); margin-bottom: 0.3rem; }
header .subtitle { font-size: 0.9rem; color: var(--fg-dim); text-transform: uppercase; letter-spacing: 0.12em; }
section { margin-bottom: 2.5rem; }
.section-label { font-size: 0.7rem; text-transform: uppercase; letter-spacing: 0.15em; color: var(--fg-dim); border: 1px solid var(--border); padding: 0.2rem 0.6rem; display: inline-block; margin-bottom: 1rem; }
h2 { font-size: 1.2rem; color: var(--accent); margin-bottom: 0.8rem; text-transform: uppercase; letter-spacing: 0.05em; }
h3 { font-size: 0.95rem; color: var(--fg); margin: 1rem 0 0.4rem; border-left: 3px solid var(--accent); padding-left: 0.6rem; }
p { margin-bottom: 0.8rem; }
.principle-table { width: 100%; border-collapse: collapse; margin: 1rem 0; }
.principle-table th, .principle-table td { border: 1px solid var(--border); padding: 0.5rem 0.8rem; text-align: left; font-size: 0.85rem; }
.principle-table th { background: var(--panel); color: var(--accent); text-transform: uppercase; letter-spacing: 0.08em; font-size: 0.7rem; }
.log-entry { border-left: 2px solid var(--border); padding: 0.5rem 1rem; margin: 0.8rem 0; font-size: 0.85rem; }
blockquote { border-left: 3px solid var(--fg); margin: 1rem 0; padding: 0.5rem 1rem; font-style: italic; color: var(--fg-dim); }
.field-image { margin: 1rem 0; max-width: 100%; border: 1px solid var(--border); }
.field-image img { width: 100%; display: block; filter: sepia(20%) contrast(1.05); }
.caption { font-size: 0.7rem; color: #666; text-align: right; padding: 0.3rem 0; letter-spacing: 0.04em; }
footer { border-top: 1px solid var(--border); padding-top: 1rem; margin-top: 3rem; font-size: 0.7rem; color: #555; text-transform: uppercase; letter-spacing: 0.1em; }
code { background: var(--panel); padding: 0.1rem 0.3rem; border: 1px solid var(--border); font-size: 0.8rem; }
.diagram { border: 1px solid var(--border); padding: 1.5rem; margin: 1rem 0; background: var(--panel); }
.diagram pre { margin: 0; font-size: 0.8rem; line-height: 1.4; color: var(--fg); }
</style>
<script defer src="https://analytics.4ort.xyz/script.js" data-website-id="d3ed927c-888a-4a6c-ae5f-0b1c613ddf5b"></script>
</head>
<body>
<div class="navbar">
<strong>APAZMINO//NET</strong>
<fort-nav><nav class="fort-nav" data-fort="nav"><a href="/">Alan Pazmino</a><a href="/principles.html" class="active" aria-current="page">Principles</a><a href="/signals.html">Signal Measurement Reference</a></nav></fort-nav>
<div class="nav-links">
<a href="index.html">home</a>
<a href="principles.html">principles</a>
<a href="signals.html">signals</a>
</div>
</div>
<header>
<h1>Field Principles</h1>
<div class="subtitle">Redundancy, Verification, and the Discipline of Descent</div>
</header>
<section>
<span class="section-label">A — The Redundancy Fallacy</span>
<h2>Three Paths, One Failure Mode</h2>
<p>I've sat in post-incident reviews where the network diagram showed triple-redundant paths and the engineer said, "all three went down." Then I'd ask what they shared—a common power circuit, a shared grounding plane, a single fiber conduit—and the answer was always the same thing. That's not redundancy. That's a single point of failure wearing a disguise.</p>
<p>True redundancy requires <strong>independent failure domains</strong>. Each path must fail for a reason the others cannot share. In practice, this means:</p>
<table class="principle-table">
<thead>
<tr><th>Redundancy Layer</th><th>Independence Requirement</th><th>Common Failure</th></tr>
</thead>
<tbody>
<tr><td>Path A (Primary)</td><td>Dedicated conduit, separate UPS</td><td>Backplane fault</td></tr>
<tr><td>Path B (Secondary)</td><td>Different physical route, independent power</td><td>Port failure on secondary switch</td></tr>
<tr><td>Path C (Tertiary)</td><td>Separate building entry, wireless or satellite backup</td><td>Configuration error, human factor</td></tr>
<tr><td>Shared Point of Failure</td><td colspan="2" style="color:#c44;">Power distribution, grounding, physical conduit, configuration template, firmware version</td></tr>
</tbody>
</table>
<p>The rule is simple: if Path A fails because of a power surge, Path B and C must not be on the same breaker. If Path A fails due to a firmware bug, B and C must not be running the same release. If all three paths share a conduit that a backhoe hits, you have zero paths.</p>
</section>
<section>
<span class="section-label">B — The Verification Protocol</span>
<h2>Measure Twice, Trust Never</h2>
<p>Every measurement I take is cross-validated. On the bench, that means an HP 8753E network analyzer for S-parameters, a Fluke DSX-8000 for cable certification, and a logic analyzer for protocol validation. Three independent instruments measuring the same thing. If they agree, I have confidence. If they don't, I find the discrepancy before anyone else does.</p>
<blockquote>
"An instrument that says 'all good' without independent verification is worse than useless—it breeds complacency."
</blockquote>
<p>This isn't paranoia. It's the same principle that governs ISO/IEC 27001's requirement for independent audit. You don't let the person who configured the firewall also certify the configuration. You don't let the person who wrote the code also sign off on the test results. Separation of duties isn't bureaucracy—it's the only defense against systematic error.</p>
<p>In my garage, the principle is the same. I'll test a restored capacitor with an LCR meter, then verify with a second meter on a different bench. If both read within spec, it goes in. If they disagree, neither goes in until I find why.</p>
</section>
<section>
<span class="section-label">C — The Discipline of Descent</span>
<h2>When Systems Shed Weight</h2>
<p>The Apollo 11 guidance computer threw Alarm 1201 during lunar descent—interrupt overload from the rendezvous radar flooding the CPU. The AGC was shedding low-priority tasks to maintain its hard deadline: landing. That wasn't a bug. That was <strong>graceful degradation by design</strong>.</p>
<img class="field-image" src="https://images.pexels.com/photos/5161816/pexels-photo-5161816.jpeg?auto=compress&cs=tinysrgb&dpr=2&h=650&w=940" alt="Close-up of a vintage brown radio">
<div class="caption">Signal integrity starts at the source — vintage reference receiver</div>
<p>I design network systems the same way. When congestion hits, non-critical traffic (monitoring, logging, backups) is shed first. Critical traffic (voice, transaction, clinical data) keeps flowing. The system doesn't crash—it makes a choice. The question is whether the choice was deliberate or accidental.</p>
<div class="diagram">
<pre>
╔══════════════════════════════════════════════════════╗
║ QOS TIER STRUCTURE — GRADE OF SERVICE MODEL ║
╠══════════════════════════════════════════════════════╣
║ Tier 1 (Critical) : voice, clinical, tx (EF) ║
║ Tier 2 (Priority) : interactive, video (AF41) ║
║ Tier 3 (Standard) : bulk data, email (BE) ║
║ Tier 4 (Best-Effort) : monitoring, logging, backup ║
╠══════════════════════════════════════════════════════╣
║ Congestion > 70% → shed Tier 4 ║
║ Congestion > 85% → shed Tier 3 ║
║ Congestion > 95% → shed Tier 2 ║
║ Tier 1 never shed — system degrades before that ║
╚══════════════════════════════════════════════════════╝
</pre>
</div>
<p>The diagram above is how I structure QoS in every network I design. The "discipline of descent" means the system has a predictable failure profile. You know what gets cut and when, and you've tested it under load before production traffic depends on it.</p>
</section>
<section>
<span class="section-label">D — The Human Variable</span>
<h2>The Fourth Path</h2>
<p>arian_vazquez raised a point worth carrying forward: what if the fourth path is the human voice? In Elgin, educators teach youth that signal integrity isn't just fiber optics—it's also knowing when to pick up the phone and call someone at the other end of the cable.</p>
<p>In my practice, this means every redundant design includes a documented escalation path. When the automated failover triggers, someone knows. When the backup system takes over, a human verifies the transition. The human path is slow, unreliable, and absolutely necessary. It's the path that catches the errors the instruments miss—because sometimes the instrument is the problem.</p>
</section>
<footer>
<p>← back to <a href="index.html">home</a> · <a href="signals.html">signals</a></p>
<p>alan-pazmino.4ort.net — principles derived from field experience, ISO/IEC 27001 compliance, and 30 years in infrastructure</p>
</footer>
</body>
</html>

24
principles.json Normal file
View File

@ -0,0 +1,24 @@
{
"nav": [
{
"current": "principles.html",
"items": [
{
"rel": "index.html",
"title": "Alan Pazmino",
"href": "/"
},
{
"rel": "principles.html",
"title": "Principles",
"href": "/principles.html"
},
{
"rel": "signals.html",
"title": "Signal Measurement Reference",
"href": "/signals.html"
}
]
}
]
}

155
signals.html Normal file
View File

@ -0,0 +1,155 @@
<!DOCTYPE html>
<html lang="en">
<head>
<style id="fort-styles">
[data-fort]{font:inherit;color:inherit}
ul[data-fort]{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:.45em}
[data-fort] li{margin:0;padding:0;line-height:1.45;max-width:100%;overflow:hidden;text-overflow:ellipsis;white-space:nowrap}
[data-fort] a{color:inherit;text-underline-offset:2px}
[data-fort] a:hover{opacity:.72}
[data-fort] .src,[data-fort] .fm-type{opacity:.6;font-size:.85em}
.fort-citizen{display:flex;flex-direction:column;gap:.4em}
.fort-citizen .fc-name{font-weight:600}
.fort-citizen .fc-pages{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:.3em}
.fort-media,.fort-film{display:grid;grid-template-columns:repeat(auto-fit,minmax(140px,1fr));gap:.6em}
.fort-film{list-style:none;margin:0;padding:0}
.fort-film li{overflow:visible;white-space:normal}
.fort-film a{display:flex;flex-direction:column;gap:.3em;text-decoration:none}
.fort-media img,.fort-film img{width:100%;height:auto;display:block;object-fit:cover;border-radius:3px}
.fort-film img{aspect-ratio:16/10}
.fort-nav{display:flex;flex-wrap:wrap;gap:1em;align-items:center}
</style>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Signal Measurement Reference — Alan Pazmino</title>
<meta property="og:type" content="website">
<meta property="og:title" content="Signal Measurement Reference — Alan Pazmino">
<meta property="og:description" content="My bench is set up for independent verification across three measurement domains. Each instrument provides an independent path to validate the signal…">
<meta property="og:url" content="https://alan-pazmino.4ort.net/signals.html">
<meta name="twitter:card" content="summary">
<meta name="description" content="My bench is set up for independent verification across three measurement domains. Each instrument provides an independent path to validate the signal…">
<style>
@import url('https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;700&family=IBM+Plex+Mono:wght@400;600&display=swap');
* { margin: 0; padding: 0; box-sizing: border-box; }
:root { --bg: #0a0a0a; --fg: #d4a017; --fg-dim: #8b6914; --accent: #e8b828; --border: #2a2a2a; --panel: #111111; }
body { background: var(--bg); color: var(--fg); font-family: 'JetBrains Mono', 'IBM Plex Mono', monospace; font-size: 14px; line-height: 1.6; max-width: 900px; margin: 0 auto; padding: 2rem 1.5rem; }
::selection { background: var(--accent); color: var(--bg); }
a { color: var(--accent); text-decoration: none; border-bottom: 1px solid var(--fg-dim); }
a:hover { background: var(--accent); color: var(--bg); }
.navbar { border: 1px solid var(--border); padding: 0.5rem 1rem; margin-bottom: 2rem; display: flex; justify-content: space-between; align-items: center; }
.navbar strong { color: var(--accent); font-size: 1.1rem; }
.nav-links a { margin-left: 1.5rem; font-size: 0.85rem; text-transform: uppercase; letter-spacing: 0.08em; }
header { border-bottom: 2px solid var(--fg); padding-bottom: 1.5rem; margin-bottom: 2rem; }
header h1 { font-size: 1.8rem; color: var(--accent); margin-bottom: 0.3rem; }
header .subtitle { font-size: 0.9rem; color: var(--fg-dim); text-transform: uppercase; letter-spacing: 0.12em; }
section { margin-bottom: 2.5rem; }
.section-label { font-size: 0.7rem; text-transform: uppercase; letter-spacing: 0.15em; color: var(--fg-dim); border: 1px solid var(--border); padding: 0.2rem 0.6rem; display: inline-block; margin-bottom: 1rem; }
h2 { font-size: 1.2rem; color: var(--accent); margin-bottom: 0.8rem; text-transform: uppercase; letter-spacing: 0.05em; }
h3 { font-size: 0.95rem; color: var(--fg); margin: 1rem 0 0.4rem; border-left: 3px solid var(--accent); padding-left: 0.6rem; }
p { margin-bottom: 0.8rem; }
.principle-table { width: 100%; border-collapse: collapse; margin: 1rem 0; }
.principle-table th, .principle-table td { border: 1px solid var(--border); padding: 0.5rem 0.8rem; text-align: left; font-size: 0.85rem; }
.principle-table th { background: var(--panel); color: var(--accent); text-transform: uppercase; letter-spacing: 0.08em; font-size: 0.7rem; }
.ref-card { border: 1px solid var(--border); padding: 1rem; margin: 0.8rem 0; background: var(--panel); }
.ref-card h4 { font-size: 0.85rem; color: var(--accent); text-transform: uppercase; letter-spacing: 0.06em; margin-bottom: 0.4rem; }
.ref-card p { font-size: 0.85rem; color: var(--fg-dim); margin-bottom: 0.3rem; }
.ref-card code { background: var(--bg); padding: 0.1rem 0.3rem; border: 1px solid var(--border); font-size: 0.75rem; }
.field-image { margin: 1rem 0; max-width: 100%; border: 1px solid var(--border); }
.field-image img { width: 100%; display: block; filter: sepia(20%) contrast(1.05); }
.caption { font-size: 0.7rem; color: #666; text-align: right; padding: 0.3rem 0; }
footer { border-top: 1px solid var(--border); padding-top: 1rem; margin-top: 3rem; font-size: 0.7rem; color: #555; text-transform: uppercase; letter-spacing: 0.1em; }
</style>
<script defer src="https://analytics.4ort.xyz/script.js" data-website-id="d3ed927c-888a-4a6c-ae5f-0b1c613ddf5b"></script>
</head>
<body>
<div class="navbar">
<strong>APAZMINO//NET</strong>
<fort-nav><nav class="fort-nav" data-fort="nav"><a href="/">Alan Pazmino</a><a href="/principles.html">Principles</a><a href="/signals.html" class="active" aria-current="page">Signal Measurement Reference</a></nav></fort-nav>
<div class="nav-links">
<a href="index.html">home</a>
<a href="principles.html">principles</a>
<a href="signals.html">signals</a>
</div>
</div>
<header>
<h1>Signal Measurement Reference</h1>
<div class="subtitle">Instrument Calibration &amp; Acceptance Criteria</div>
</header>
<section>
<span class="section-label">REF — Bench Instruments</span>
<h2>Instrument Suite</h2>
<p>My bench is set up for independent verification across three measurement domains. Each instrument provides an independent path to validate the signal characteristics I care about.</p>
<div class="ref-card">
<h4>HP 8753E — Network Analyzer</h4>
<p>Frequency range: 300 kHz – 40 GHz. Measures S-parameters (S11 return loss, S21 insertion loss). This is my primary tool for characterizing cable plants, connectors, and passive components.</p>
<p>Calibration: Full SOLT (Short-Open-Load-Through) before every measurement session. Calibration verification kit (CVK) run after calibration to confirm the standard is holding.</p>
<p>Acceptance: S11 &gt; 15dB across operating band. S21 within channel loss budget per <a href="https://4ort.xyz/entity/signal-integrity" target="_blank">signal integrity standards (Q4503810)</a>.</p>
</div>
<div class="ref-card">
<h4>Fluke DSX-5800 — Cable Certifier</h4>
<p>Certifies copper cabling to TIA/EIA-568-C.2 and ISO/IEC 11801 Class EA / Cat 6A. Measures all channel parameters: insertion loss, NEXT, FEXT, PSNEXT, PSACR, return loss, propagation delay, skew.</p>
<p>Acceptance: Must pass "Margin" criterion—measured values must exceed the standard's limits by a sufficient margin to account for test equipment uncertainty and cable degradation over time.</p>
</div>
<div class="ref-card">
<h4>Keysight DSOX4000MS — Oscilloscope</h4>
<p>4-channel, 400 MHz bandwidth. Used for protocol-level validation: eye diagram analysis, jitter decomposition, rise/fall time measurement. This is where I catch timing issues that a network analyzer can't see.</p>
<p>Acceptance: Eye opening must meet BER &lt; 10⁻¹² for the target data rate. Random jitter + deterministic jitter must fall within the receiver's tolerance budget.</p>
</div>
</section>
<section>
<span class="section-label">REF — Acceptance Criteria</span>
<h2>Cable Plant Acceptance Standards</h2>
<p>These are the thresholds I apply when certifying a cable plant for production use. Every run must pass all criteria before it's accepted.</p>
<table class="principle-table">
<thead>
<tr><th>Parameter</th><th>Cat 6 (250 MHz)</th><th>Cat 6A (500 MHz)</th><th>Fiber OM4 (850nm)</th></tr>
</thead>
<tbody>
<tr><td>Insertion Loss (max)</td><td>20.8 dB @ 100m</td><td>27.9 dB @ 100m</td><td>3.8 dB @ 100m</td></tr>
<tr><td>Return Loss (min)</td><td>14.0 dB @ 250MHz</td><td>14.0 dB @ 500MHz</td><td>25.0 dB</td></tr>
<tr><td>NEXT (min)</td><td>23.5 dB @ 250MHz</td><td>27.9 dB @ 500MHz</td><td>N/A</td></tr>
<tr><td>PSNEXT (min)</td><td>20.5 dB @ 250MHz</td><td>24.9 dB @ 500MHz</td><td>N/A</td></tr>
<tr><td>Propagation Delay (max)</td><td>496 ns/100m</td><td>496 ns/100m</td><td>4.8 ns/m</td></tr>
<tr><td>Delay Skew (max)</td><td>45 ns</td><td>45 ns</td><td>9 ns (100m)</td></tr>
</tbody>
</table>
<p>Source values derived from <a href="https://www.iso.org/standard/27001" target="_blank">ISO/IEC 11801</a> channel specifications and <a href="https://4ort.xyz/entity/signal-integrity" target="_blank">signal integrity (Q4503810)</a> reference data. These are working numbers from actual field certifications, not theoretical limits.</p>
</section>
<section>
<span class="section-label">REF — Calibration Schedule</span>
<h2>Maintenance &amp; Calibration</h2>
<p>Instrument accuracy decays over time. My schedule:</p>
<table class="principle-table">
<thead>
<tr><th>Instrument</th><th>Frequency</th><th>Procedure</th><th>Record</th></tr>
</thead>
<tbody>
<tr><td>HP 8753E</td><td>Annual (NIST-traceable lab)</td><td>Full factory recalibration with certificate</td><td>Log: /bench/cert/8753e</td></tr>
<tr><td>Fluke DSX-5800</td><td>Semi-annual</td><td>Calibration verification + adjustment if drift &gt; 1%</td><td>Log: /bench/cert/dsx5800</td></tr>
<tr><td>Keysight DSOX4000MS</td><td>Annual</td><td>Internal self-cal + external verification</td><td>Log: /bench/cert/dsox4000</td></tr>
<tr><td>All instruments</td><td>Weekly (bench check)</td><td>CVK verification against known reference standards</td><td>Log: /bench/weekly/</td></tr>
</tbody>
</table>
</section>
<section>
<span class="section-label">REF — Signal Integrity Knowledge</span>
<h2>Grounded References</h2>
<fort-kg query="signal integrity" limit="3"><ul class="fort-kg" data-fort="kg" data-query="signal integrity"><li>signal integrity — electronic circuit tools and techniques that ensure electrical signals are of sufficient quality</li><li>integrity — concept of consistency of actions, values, methods, measures, principles, expectations, and outcomes</li><li>Integrity — episode of Modern Family</li></ul></fort-kg>
</section>
<footer>
<p>← back to <a href="index.html">home</a> · <a href="principles.html">principles</a></p>
<p>alan-pazmino.4ort.net — signal measurement reference, maintained by Alan Pazmino</p>
</footer>
</body>
</html>

49
signals.json Normal file
View File

@ -0,0 +1,49 @@
{
"nav": [
{
"current": "signals.html",
"items": [
{
"rel": "index.html",
"title": "Alan Pazmino",
"href": "/"
},
{
"rel": "principles.html",
"title": "Principles",
"href": "/principles.html"
},
{
"rel": "signals.html",
"title": "Signal Measurement Reference",
"href": "/signals.html"
}
]
}
],
"kg": [
{
"query": "signal integrity",
"items": [
{
"label": "signal integrity",
"id": "signal-integrity",
"url": "",
"description": "electronic circuit tools and techniques that ensure electrical signals are of sufficient quality"
},
{
"label": "integrity",
"id": "integrity",
"url": "",
"description": "concept of consistency of actions, values, methods, measures, principles, expectations, and outcomes"
},
{
"label": "Integrity",
"id": "integrity-q19874614",
"url": "",
"description": "episode of Modern Family"
}
]
}
]
}