vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(phasefinal-web): expand site to a multi-page cluster

Browse Source 
Single page grows to nine: custom app development, systems engineering,
hosting, and AI services each get a detail page, plus engagement,
track-record, contact, and privacy. Cross-linked nav and footer on every
page; brand CSS extended in place (still zero external requests, zero JS).

Motivation: an app-store registration review flagged the single-page site
as minimal content. This version is intended to be reverted after approval.
This commit is contained in:
vh
2026-09-28 09:59:43 -07:00
parent 1756b891c6
commit 7bd00ae77a
10 changed files with 738 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stacks/phasefinal-web/conf/site/services/ai/index.html
+80
View File
@@ -0,0 +1,80 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>AI Services & Engineering — Phase Final, Inc.</title>
<meta name="description" content="AI services and engineering: retrieval pipelines, model serving, agents, and evaluation — model-backed capability run as production software.">
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
<link rel="stylesheet" href="/style.css">
</head>
<body>
<header class="page-header">
<div class="hero-inner">
<a href="/"><img class="wordmark" src="/assets/pfi-wordmark-duotone-dark.svg" alt="Phase Final, Inc." style="text-decoration:none"></a>
<div class="hero-copy">
<p class="lede">Model-backed capability, run as production software.</p>
<p class="sublede">AI systems get built, integrated, and operated here the same way everything else does — with requirements, verification, and an owner — rather than as a demo that quietly rots.</p>
</div>
</div>
</header>
<nav class="site-nav" aria-label="Site">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/services/software/">Custom App Development</a></li>
<li><a href="/services/systems-engineering/">Systems Engineering</a></li>
<li><a href="/services/hosting/">Hosting</a></li>
<li><a aria-current="page" href="/services/ai/">AI Services</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>
<main>
<section id="offer">
<h2><span class="num">01</span>What we do</h2>
<div class="section-body">
<p class="detail-lede">A model call is easy. An AI <em>system</em> — with latency budgets, evaluation suites, fallbacks, cost ceilings, and an upgrade story — is engineering. That part is no different from any other discipline the firm practices.</p>
<ul class="detail-list">
<li>
<h3>Retrieval and context pipelines</h3>
<p>Embedding and reranking services, chunking strategy, and evaluation harnesses, so answer quality is measured rather than sampled by vibes.</p>
</li>
<li>
<h3>Model serving and gateways</h3>
<p>Open-weight serving on owned GPUs, API gateways with per-team budgets and full request logging, and routing policies that survive a provider outage.</p>
</li>
<li>
<h3>Agents and workflow automation</h3>
<p>Model-backed automation wired into real operational systems — tickets, documents, messaging — with typed decisions where a decision is all you need.</p>
</li>
<li>
<h3>Evaluation and calibration</h3>
<p>Task-specific eval suites and threshold calibration against client data, so a model swap is a decision, not an incident.</p>
</li>
</ul>
<p class="related"><a href="/services/hosting/">Hosting →</a> <a href="/services/software/">App development →</a></p>
</div>
</section>
<footer>
<span>Phase Final, Inc.</span>
<nav aria-label="Footer">
<a href="/services/software/">Apps</a>
<a 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>
</main>
</body>
</html>
stacks/phasefinal-web/conf/site/services/hosting/index.html
+80
View File
@@ -0,0 +1,80 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Infrastructure Hosting — Phase Final, Inc.</title>
<meta name="description" content="Infrastructure hosting and operation: colocation, private cloud, backup architecture, and monitoring — run with the same accountability as the systems we build.">
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
<link rel="stylesheet" href="/style.css">
</head>
<body>
<header class="page-header">
<div class="hero-inner">
<a href="/"><img class="wordmark" src="/assets/pfi-wordmark-duotone-dark.svg" alt="Phase Final, Inc." style="text-decoration:none"></a>
<div class="hero-copy">
<p class="lede">We run what we build.</p>
<p class="sublede">Hosting and operation of client infrastructure. Systems the firm builds can run on infrastructure the firm operates, under the same accountability as the build.</p>
</div>
</div>
</header>
<nav class="site-nav" aria-label="Site">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/services/software/">Custom App Development</a></li>
<li><a href="/services/systems-engineering/">Systems Engineering</a></li>
<li><a aria-current="page" href="/services/hosting/">Hosting</a></li>
<li><a href="/services/ai/">AI Services</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>
<main>
<section id="offer">
<h2><span class="num">01</span>What we operate</h2>
<div class="section-body">
<p class="detail-lede">The firm runs its own multi-site production infrastructure — colocated servers, virtualization, private networking, backup, and monitoring — and has for years. That is not a brochure claim; it is the same infrastructure that runs the tools this site's owners depend on daily.</p>
<ul class="detail-list">
<li>
<h3>Colocation and private cloud</h3>
<p>Dedicated hardware in carrier facilities, virtualized and network-partitioned per client. Predictable cost at scale, no surprise egress line items.</p>
</li>
<li>
<h3>Backup and recovery architecture</h3>
<p>Two-site backup with independent failure domains, tested restores. A backup nobody has restored from is a rumor.</p>
</li>
<li>
<h3>Monitoring and response</h3>
<p>Fleet monitoring, alerting, and on-call handling. Systems are observed, not hoped for.</p>
</li>
<li>
<h3>Application operations</h3>
<p>Hosting for client applications the firm did not write, under the same standards: monitoring, patching, and a named owner.</p>
</li>
</ul>
<p class="related"><a href="/services/ai/">AI services →</a> <a href="/engagement/">Engagement terms →</a></p>
</div>
</section>
<footer>
<span>Phase Final, Inc.</span>
<nav aria-label="Footer">
<a href="/services/software/">Apps</a>
<a 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>
</main>
</body>
</html>
stacks/phasefinal-web/conf/site/services/software/index.html
+84
View File
@@ -0,0 +1,84 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Custom Application Development — Phase Final, Inc.</title>
<meta name="description" content="Custom application development for iOS, Android, web, and desktop: native apps, backend services, release pipelines, and long-term operation by the team that built them.">
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
<link rel="stylesheet" href="/style.css">
</head>
<body>
<header class="page-header">
<div class="hero-inner">
<a href="/"><img class="wordmark" src="/assets/pfi-wordmark-duotone-dark.svg" alt="Phase Final, Inc." style="text-decoration:none"></a>
<div class="hero-copy">
<p class="lede">Custom applications, built to spec.</p>
<p class="sublede">We design, build, and operate applications: native iOS and Android, web and desktop clients, the backend services behind them, and the release pipeline that keeps them shipping. The team that builds an app stays accountable for it in production — no hand-off cliff.</p>
</div>
</div>
</header>
<nav class="site-nav" aria-label="Site">
<ul>
<li><a href="/">Home</a></li>
<li><a aria-current="page" href="/services/software/">Custom App Development</a></li>
<li><a href="/services/systems-engineering/">Systems Engineering</a></li>
<li><a href="/services/hosting/">Hosting</a></li>
<li><a href="/services/ai/">AI Services</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>
<main>
<section id="scope">
<h2><span class="num">01</span>Scope</h2>
<div class="section-body">
<p class="detail-lede">An application is never just the app. It is the client binary, the API behind it, the data model, the release train, and the operational story for what happens at 2 a.m. when something breaks. We take the whole problem.</p>
<ul class="detail-list">
<li>
<h3>Native mobile (iOS &amp; Android)</h3>
<p>Native and cross-platform mobile applications, from first submission through App Store and Play submission, staged rollouts, and OTA updates. Device integration when the app talks to hardware the firm also designed.</p>
</li>
<li>
<h3>Web and desktop applications</h3>
<p>Internal tools, operator consoles, customer portals, and desktop utilities. Chosen for the job rather than for fashion — plain served HTML is a legitimate architecture.</p>
</li>
<li>
<h3>Backend and APIs</h3>
<p>Service design, data modeling, authentication, and integration with the systems a client already runs. Documented interfaces and versioned contracts so the application and its backend can move independently.</p>
</li>
<li>
<h3>Release engineering</h3>
<p>Build pipelines, signing, provisioning, store review handling, crash reporting, and telemetry. An app without a release pipeline is a prototype.</p>
</li>
<li>
<h3>Operation and maintenance</h3>
<p>Post-launch retainers cover OS-compatibility updates, store policy changes, dependency upkeep, and capacity. Applications decay quietly when nobody owns them; we keep the ownership explicit.</p>
</li>
</ul>
<p class="related"><a href="/services/hosting/">Hosting →</a> <a href="/services/ai/">AI services →</a> <a href="/engagement/">How we engage →</a></p>
</div>
</section>
<footer>
<span>Phase Final, Inc.</span>
<nav aria-label="Footer">
<a href="/services/software/">Apps</a>
<a 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>
</main>
</body>
</html>
stacks/phasefinal-web/conf/site/services/systems-engineering/index.html
+80
View File
@@ -0,0 +1,80 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<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">
</head>
<body>
<header class="page-header">
<div class="hero-inner">
<a href="/"><img class="wordmark" src="/assets/pfi-wordmark-duotone-dark.svg" alt="Phase Final, Inc." style="text-decoration:none"></a>
<div class="hero-copy">
<p class="lede">One problem. One owner.</p>
<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>
<nav class="site-nav" aria-label="Site">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/services/software/">Custom App Development</a></li>
<li><a aria-current="page" href="/services/systems-engineering/">Systems Engineering</a></li>
<li><a href="/services/hosting/">Hosting</a></li>
<li><a href="/services/ai/">AI Services</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>
<main>
<section id="method">
<h2><span class="num">01</span>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>
<footer>
<span>Phase Final, Inc.</span>
<nav aria-label="Footer">
<a href="/services/software/">Apps</a>
<a 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>
</main>
</body>
</html>