vh
85f8a3a072
The 2026-09-28 expansion grew the one-page design to nine pages by bolting a nav band under each hero. This makes the cluster one site: - One site header on every page: the wordmark (home link) and a single row of short, consistent labels (Applications, Systems, Hosting, AI, Engagement, Track record, Contact). The nav no longer wraps into two rows at desktop width or four on a phone. - A real <h1> on every page (the title was a <p>), a skip link, and one footer outside <main> on every page, home included. - The contact page was unreadable: its section borrowed the home page's dark contact-card id, so its copy was grey on near-black (2.3:1) and its headings measured 1.0:1. It is an ordinary section now. - Section numbers only where there is a sequence (home, engagement). - The spec bar names all four services; it stacks cleanly on a phone. - Contrast: --text-tertiary 4.3:1 -> 4.96:1, --accent-text 4.36:1 -> 4.74:1 on paper. Track-record labels drop tracked capitals. - The grid behind the hero and the contact card is its own layer; the contact card loses its left side-tab stripe. - The stylesheet link is versioned (style.css?v=2026-09-28): CSS is cached for an hour, and the new markup must not meet the old styles. - README: nine pages, the shared structure, the CSS-version rule, and the operator's anti-slop waivers (the hero's volt rule, Space Grotesk). Copy is unchanged apart from nav labels (the brief's legal constraints hold). Still zero JavaScript and zero external requests. Impeccable detector (controls 7/0, static + rendered at 1280 and 390, light and dark): 200 unwaived -> 54, all of them the two waived brand devices; two identical runs. Operator: "ship the site cleanup, keep the rule and the font".
86 lines
3.5 KiB
HTML
86 lines
3.5 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<meta name="theme-color" content="#0f1318">
|
|
<title>Systems Engineering — Phase Final, Inc.</title>
|
|
<meta name="description" content="Systems engineering: requirements, architecture, implementation, and verification of integrated hardware and software systems, treated as one problem with one owner.">
|
|
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
|
|
<link rel="stylesheet" href="/style.css?v=2026-09-28">
|
|
</head>
|
|
<body>
|
|
|
|
<a class="skip" href="#main">Skip to content</a>
|
|
<header class="site-header">
|
|
<div class="site-header-inner">
|
|
<a class="brand" href="/"><img src="/assets/pfi-wordmark-duotone-dark.svg" alt="Phase Final, Inc." width="98" height="28"></a>
|
|
<nav class="site-nav" aria-label="Site">
|
|
<ul>
|
|
<li><a href="/services/software/">Applications</a></li>
|
|
<li><a aria-current="page" href="/services/systems-engineering/">Systems</a></li>
|
|
<li><a href="/services/hosting/">Hosting</a></li>
|
|
<li><a href="/services/ai/">AI</a></li>
|
|
<li><a href="/engagement/">Engagement</a></li>
|
|
<li><a href="/track-record/">Track record</a></li>
|
|
<li><a href="/contact/">Contact</a></li>
|
|
</ul>
|
|
</nav>
|
|
</div>
|
|
</header>
|
|
|
|
<header class="page-header">
|
|
<div class="hero-inner">
|
|
<div class="hero-copy">
|
|
<h1 class="lede">One problem. One owner.</h1>
|
|
<p class="sublede">Requirements, architecture, implementation, and verification are treated as one problem with one owner. That is the difference between systems engineering and a chain of hand-offs.</p>
|
|
</div>
|
|
</div>
|
|
</header>
|
|
|
|
<main id="main">
|
|
|
|
<section id="method">
|
|
<h2>Method</h2>
|
|
<div class="section-body">
|
|
<p class="detail-lede">Most engineering failures between disciplines happen in the seams: firmware blames the app, the app blames the API, the API blames the infrastructure. Systems engineering is the discipline of refusing those seams — one accountable owner across the stack.</p>
|
|
<ul class="detail-list">
|
|
<li>
|
|
<h3>Requirements and constraints</h3>
|
|
<p>Written down, ranked, and testable before anybody builds. A requirement you cannot verify is a wish.</p>
|
|
</li>
|
|
<li>
|
|
<h3>Architecture</h3>
|
|
<p>Partitioning hardware, firmware, software, and infrastructure so each piece can fail, ship, and evolve in the way that is actually cheap.</p>
|
|
</li>
|
|
<li>
|
|
<h3>Implementation</h3>
|
|
<p>Firmware, applications, services, and infrastructure built by the same team that drew the boxes, so the drawing stays honest.</p>
|
|
</li>
|
|
<li>
|
|
<h3>Verification</h3>
|
|
<p>Every requirement traced to a test that can fail. Field data feeds the next revision rather than the next excuse.</p>
|
|
</li>
|
|
</ul>
|
|
<p class="related"><a href="/track-record/">Track record →</a> <a href="/services/software/">App development →</a></p>
|
|
</div>
|
|
</section>
|
|
|
|
</main>
|
|
|
|
<footer class="site-footer">
|
|
<span>Phase Final, Inc.</span>
|
|
<nav aria-label="Footer">
|
|
<a href="/services/software/">Applications</a>
|
|
<a aria-current="page" href="/services/systems-engineering/">Systems</a>
|
|
<a href="/services/hosting/">Hosting</a>
|
|
<a href="/services/ai/">AI</a>
|
|
<a href="/engagement/">Engagement</a>
|
|
<a href="/track-record/">Track record</a>
|
|
<a href="/contact/">Contact</a>
|
|
<a href="/privacy/">Privacy</a>
|
|
</nav>
|
|
</footer>
|
|
</body>
|
|
</html>
|