Source identity
| Field | Recorded value |
|---|---|
| Source type | GitHub source |
| Original record | Janady13/missionmatch / docs/presentation/missionmatch_presentation.html |
| Date | Not specified in source |
| Repository | Janady13/missionmatch |
| Revision | 720d47fae476b0d38477ae4401697d372b1ea2bc |
| Branch | feature/opportunity-to-outcome |
| Path or archive member | docs/presentation/missionmatch_presentation.html |
| Original SHA-256 | d1f8c207e5ddad3c304779f84573927b8f497221b546a432b767c504adbfc161 |
| Git blob SHA | 3c7ec617761e729b6387055603852a360ba7ba89 |
| Reading-copy SHA-256 | d1f8c207e5ddad3c304779f84573927b8f497221b546a432b767c504adbfc161 |
Recovered source transcript
Download complete source text ↓788 lines · 53.3 KB
<!DOCTYPE html>
<!--
missionMATCH client presentation. Hand authored HTML, rendered to PDF by headless Chrome. No program
generates this markup. Brand palette per the project brand guide. Confidential and proprietary.
-->
<html lang="en">
<head>
<meta charset="utf-8">
<title>missionMATCH Platform Presentation</title>
<style>
:root{
--navy:#0F2744; --steel:#2E5EAA; --gold:#D4A017; --gray:#F4F6F8;
--ink:#1a2331; --muted:#5b6b7f; --line:#dfe5ec; --green:#1f8a4c; --amber:#b5850f; --red:#b23a3a;
}
*{box-sizing:border-box;}
html,body{margin:0;padding:0;}
body{font-family:"Helvetica Neue",Arial,sans-serif;color:var(--ink);font-size:13px;line-height:1.55;}
h1,h2,h3,h4{color:var(--navy);margin:0 0 .5em;line-height:1.2;font-weight:700;}
h2{font-size:23px;border-bottom:3px solid var(--gold);padding-bottom:6px;margin-top:0;}
h3{font-size:16px;color:var(--steel);margin-top:1.2em;}
h4{font-size:13px;color:var(--navy);margin-top:1em;letter-spacing:.02em;text-transform:uppercase;}
p{margin:0 0 .8em;}
a{color:var(--steel);text-decoration:none;}
strong{color:var(--navy);}
ul,ol{margin:0 0 .8em;padding-left:1.2em;}
li{margin:.25em 0;}
code{font-family:"SF Mono",Menlo,Consolas,monospace;font-size:11.5px;background:var(--gray);padding:1px 4px;border-radius:3px;color:var(--navy);}
/* Page setup for Chrome print to pdf */
@page{size:Letter;margin:0;}
.page{
position:relative;width:8.5in;min-height:11in;padding:0.7in 0.75in 0.85in;
page-break-after:always;background:#fff;overflow:hidden;
}
.page:last-child{page-break-after:auto;}
.page-head{display:flex;justify-content:space-between;align-items:center;font-size:10px;color:var(--muted);
border-bottom:1px solid var(--line);padding-bottom:6px;margin-bottom:18px;letter-spacing:.04em;}
.page-head .brand{color:var(--navy);font-weight:700;}
.page-foot{position:absolute;bottom:0.45in;left:0.75in;right:0.75in;display:flex;justify-content:space-between;
font-size:9px;color:var(--muted);border-top:1px solid var(--line);padding-top:6px;letter-spacing:.03em;}
.confidential-tag{color:var(--gold);font-weight:700;text-transform:uppercase;letter-spacing:.12em;}
/* Cover */
.cover{background:linear-gradient(155deg,var(--navy) 0%,#16345c 55%,var(--steel) 130%);color:#fff;
display:flex;flex-direction:column;justify-content:space-between;padding:1.1in 0.9in;}
.cover h1{color:#fff;font-size:52px;letter-spacing:-.5px;margin:0;}
.cover .tm{color:var(--gold);font-size:52px;vertical-align:super;font-size:22px;}
.cover .sub{color:#cfe0f5;font-size:19px;font-weight:400;margin-top:10px;max-width:6in;line-height:1.4;}
.cover .rule{height:4px;width:120px;background:var(--gold);margin:26px 0;}
.cover .tools{display:flex;flex-wrap:wrap;gap:12px;margin-top:8px;max-width:6.8in;}
.cover .tool{border:1px solid rgba(255,255,255,.35);border-radius:7px;padding:11px 14px;width:3.2in;}
.cover .tool .n{color:var(--gold);font-weight:700;font-size:15px;}
.cover .tool .d{color:#dbe7f7;font-size:11px;margin-top:3px;}
.cover .foot{color:#aec4e2;font-size:11px;}
.cover .stamp{border:2px solid var(--gold);color:var(--gold);font-weight:700;text-transform:uppercase;
letter-spacing:.14em;font-size:11px;padding:7px 13px;border-radius:5px;display:inline-block;}
/* Components */
.lead{font-size:15px;color:var(--muted);margin-bottom:1.1em;}
.grid2{display:grid;grid-template-columns:1fr 1fr;gap:14px;}
.grid3{display:grid;grid-template-columns:1fr 1fr 1fr;gap:12px;}
.card{border:1px solid var(--line);border-radius:8px;padding:13px 15px;background:#fff;}
.card.tint{background:var(--gray);}
.card .k{color:var(--steel);font-weight:700;font-size:12px;text-transform:uppercase;letter-spacing:.03em;margin-bottom:4px;}
.callout{border-left:4px solid var(--gold);background:#fdf7e8;padding:11px 15px;border-radius:0 6px 6px 0;margin:12px 0;}
.callout.navy{border-left-color:var(--steel);background:#eef3fb;}
.callout.warn{border-left-color:var(--red);background:#fbeeee;}
.pill{display:inline-block;background:var(--navy);color:#fff;border-radius:20px;padding:2px 10px;font-size:10.5px;font-weight:600;margin:2px 4px 2px 0;}
.pill.gold{background:var(--gold);color:var(--navy);}
.pill.steel{background:var(--steel);}
table{width:100%;border-collapse:collapse;margin:10px 0;font-size:12px;}
th{background:var(--navy);color:#fff;text-align:left;padding:7px 9px;font-weight:600;font-size:11px;letter-spacing:.02em;}
td{padding:6px 9px;border-bottom:1px solid var(--line);vertical-align:top;}
tr:nth-child(even) td{background:#fafbfd;}
.num{font-variant-numeric:tabular-nums;}
.step{display:flex;gap:12px;margin:10px 0;}
.step .no{flex:0 0 30px;height:30px;border-radius:50%;background:var(--navy);color:#fff;font-weight:700;
display:flex;align-items:center;justify-content:center;font-size:14px;}
.step .no.gold{background:var(--gold);color:var(--navy);}
.step .b h4{margin:.1em 0 .2em;text-transform:none;color:var(--navy);font-size:14px;}
.step .b p{margin:0;color:var(--muted);font-size:12px;}
.band{display:inline-block;width:11px;height:11px;border-radius:3px;vertical-align:middle;margin-right:5px;}
.b-green{background:var(--green);} .b-amber{background:var(--amber);} .b-red{background:var(--red);}
.kpi{display:flex;gap:12px;margin:14px 0;}
.kpi .box{flex:1;border:1px solid var(--line);border-radius:8px;padding:12px;text-align:center;background:var(--gray);}
.kpi .box .v{font-size:26px;font-weight:800;color:var(--navy);}
.kpi .box .l{font-size:10.5px;color:var(--muted);text-transform:uppercase;letter-spacing:.04em;margin-top:2px;}
.small{font-size:11px;color:var(--muted);}
.divider{height:1px;background:var(--line);margin:16px 0;}
.toc li{margin:.4em 0;font-size:14px;}
.toc .n{color:var(--gold);font-weight:700;display:inline-block;width:26px;}
.legal{font-size:11px;color:#3a4658;line-height:1.6;}
.legal h3{color:var(--navy);}
.sectiontag{color:var(--gold);font-weight:700;text-transform:uppercase;letter-spacing:.14em;font-size:11px;margin-bottom:4px;}
</style>
</head>
<body>
<!-- ============================ COVER ============================ -->
<section class="page cover">
<div>
<div class="stamp">Confidential and Proprietary</div>
</div>
<div>
<h1>missionMATCH<span class="tm">™</span></h1>
<div class="rule"></div>
<div class="sub">The Cleared Workforce Intelligence Platform for federal contractors, cleared staffing firms, and capture teams.</div>
<div class="tools">
<div class="tool"><div class="n">screenMATCH™</div><div class="d">Is this candidate qualified for this requirement?</div></div>
<div class="tool"><div class="n">slateMATCH™</div><div class="d">Who belongs on the proposal candidate slate?</div></div>
<div class="tool"><div class="n">missionMATCH™</div><div class="d">Who can support this mission today?</div></div>
<div class="tool"><div class="n">recruitMATCH™</div><div class="d">Who is working the desk, and how is it going?</div></div>
</div>
</div>
<div class="foot">
<div><strong style="color:#fff">Platform Overview, Data Flow, Architecture, and Commercial Brief</strong><br>
Prepared for prospective client review. Not for redistribution.</div>
<div style="text-align:right">Document version 1.1<br>Issued 3 August 2026</div>
</div>
</section>
<!-- ============================ CONFIDENTIALITY (front matter) ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span class="confidential-tag">Confidential</span></div>
<div class="sectiontag">Notice</div>
<h2>Confidentiality and Intellectual Property Notice</h2>
<p class="lead">Read this notice before reviewing the material that follows.</p>
<div class="callout warn">
<strong>This document and the platform it describes are confidential, proprietary, and protected.</strong>
The methods, architecture, scoring model, data flows, and product design disclosed here are trade secrets and
the intellectual property of the platform owner. They are shared solely for the purpose of evaluating a
potential commercial relationship.
</div>
<div class="grid2">
<div class="card"><div class="k">Permitted</div>
Confidential internal evaluation by the named recipient. Review by the recipient's own advisors who are
bound by equivalent confidentiality obligations.</div>
<div class="card"><div class="k">Prohibited</div>
Copying, redistribution, public posting, reverse engineering, or use of any concept, diagram, or method
herein to build, specify, or procure a competing capability.</div>
</div>
<p class="small" style="margin-top:14px">A full legal notice, including the confidentiality terms, the intellectual property reservation of rights,
the no license grant, the demo data disclaimer, and the responsible use terms, appears at the end of this
document. By continuing to read you acknowledge those terms.</p>
<div class="divider"></div>
<div class="sectiontag">Contents</div>
<ul class="toc" style="list-style:none;padding:0;margin-top:8px;">
<li><span class="n">01</span> Executive summary</li>
<li><span class="n">02</span> The problem, and why it is hard</li>
<li><span class="n">03</span> The four tools, one intelligence loop</li>
<li><span class="n">04</span> How it works, step by step data flow</li>
<li><span class="n">05</span> Platform data flow chart</li>
<li><span class="n">06</span> The scoring engine, explainable by design</li>
<li><span class="n">07</span> The AI brain, four augmentation classes over one engine</li>
<li><span class="n">08</span> Architecture and technology</li>
<li><span class="n">09</span> Responsible AI, compliance, and auditability</li>
<li><span class="n">10</span> Security and deployment posture</li>
<li><span class="n">11</span> Why we win, the commercial brief</li>
<li><span class="n">12</span> Roadmap and integration readiness</li>
<li><span class="n">13</span> Full legal notice and disclaimers</li>
</ul>
</section>
<!-- ============================ 01 EXECUTIVE SUMMARY ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>01 Executive summary</span></div>
<div class="sectiontag">Section 01</div>
<h2>Executive Summary</h2>
<p class="lead">missionMATCH turns a cleared workforce into a decision ready intelligence asset, from the moment a
requirement lands to the moment a proposal ships.</p>
<p>Government contractors win or lose on people. A single unfilled key personnel line, a clearance that lapsed,
or a slate that cannot survive an audit can sink a bid worth tens of millions. Yet most firms still run this on
spreadsheets, tribal memory, and a resume folder. missionMATCH replaces that with a single platform that reads a
requirement, scores every candidate against it with a transparent and defensible model, ranks a proposal ready
slate, and keeps a complete compliance record, all under strict tenant isolation and validated cryptography.</p>
<div class="kpi">
<div class="box"><div class="v">6</div><div class="l">Scoring dimensions</div></div>
<div class="box"><div class="v">4</div><div class="l">Purpose built tools</div></div>
<div class="box"><div class="v">4</div><div class="l">AI augmentation classes</div></div>
<div class="box"><div class="v">2</div><div class="l">Government clouds supported</div></div>
</div>
<h3>What makes it different</h3>
<div class="grid2">
<div class="card tint"><div class="k">Explainable by construction</div>
Every match score is a transparent weighted breakdown with a human readable rationale and a recordable
decision trace. This is an Automated Employment Decision Tool built to be defended, not a black box.</div>
<div class="card tint"><div class="k">Compliance is a feature, not an afterthought</div>
Demographic data is walled off from scoring entirely. The platform produces the adverse impact reporting a
buyer needs for a NYC Local Law 144 or an OFCCP style review.</div>
<div class="card tint"><div class="k">Built for the cleared world</div>
Clearance hierarchy, poly, and compartment logic are first class. Cryptography is validated to the federal
standard from day one. Cleared resumes are treated as controlled unclassified information.</div>
<div class="card tint"><div class="k">No vendor lock in</div>
The same system runs on Amazon Web Services GovCloud or Azure Government. Choosing a cloud is configuration,
not a rewrite.</div>
</div>
<div class="callout navy">
<strong>The one sentence version.</strong> missionMATCH is the system of record for the question every capture
and staffing team asks daily, who can support this mission, and it answers that question in a way a compliance
officer, a proposal manager, and a contracting officer can all trust.
</div>
</section>
<!-- ============================ 02 THE PROBLEM ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>02 The problem</span></div>
<div class="sectiontag">Section 02</div>
<h2>The Problem, and Why It Is Hard</h2>
<p class="lead">Cleared staffing is a matching problem wrapped in a compliance problem wrapped in a security problem.</p>
<div class="step"><div class="no">1</div><div class="b"><h4>The match is multidimensional</h4>
<p>A qualified candidate is not just a skills match. It is the right clearance at the right level, the right
certifications, prior experience with the customer agency, enough years, and the right place and availability.
Miss one and the candidate is not proposal ready, no matter how strong the resume reads.</p></div></div>
<div class="step"><div class="no">2</div><div class="b"><h4>The stakes are asymmetric</h4>
<p>A weak slate does not just lose a point, it can render a bid non compliant. Key personnel gaps, unsupported
clearance claims, and stale availability are the quiet reasons good companies lose recompetes.</p></div></div>
<div class="step"><div class="no">3</div><div class="b"><h4>Every decision is an employment decision</h4>
<p>Screening and ranking people for jobs is regulated. New rules on automated employment decision tools require
that scoring be explainable, that a human stays in the loop, and that adverse impact can be measured. A tool
that cannot show its work is a liability.</p></div></div>
<div class="step"><div class="no">4</div><div class="b"><h4>The data is sensitive</h4>
<p>Clearance information and cleared resumes are controlled. They cannot be sprayed across consumer software as
a service tools, logged carelessly, or sent to an unaccredited model endpoint.</p></div></div>
<div class="step"><div class="no">5</div><div class="b"><h4>The signal is scattered</h4>
<p>The intelligence that decides a bid lives in five places at once, the resume, the requirement, the
solicitation, the incumbent landscape, and the labor rate. Nobody has time to fuse it by hand before the
proposal is due.</p></div></div>
<div class="callout">
<strong>The gap in the market.</strong> Generic applicant tracking systems were built for commercial hiring at
volume. They do not understand clearances, they do not fuse federal market signal, and they were never designed
to defend an automated employment decision. missionMATCH is built for exactly this world.
</div>
</section>
<!-- ============================ 03 FOUR TOOLS ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>03 Four tools, one loop</span></div>
<div class="sectiontag">Section 03</div>
<h2>Four Tools, One Intelligence Loop</h2>
<p class="lead">One shared engine and one shared data model power three focused tools, each answering a distinct
question at a distinct moment in the capture lifecycle.</p>
<div class="grid2">
<div class="card"><div class="k">screenMATCH™</div>
<strong>Is this candidate qualified for this requirement?</strong>
<p class="small" style="margin-top:6px">A single candidate qualification view. It produces the explainable
score, the mission readiness panels, and the clearance intelligence for one person against one requirement.
This is the desk level check a recruiter runs before advancing anyone.</p></div>
<div class="card"><div class="k">slateMATCH™</div>
<strong>Who belongs on the proposal candidate slate?</strong>
<p class="small" style="margin-top:6px">The core differentiator. It scores the whole pool against a
requirement, ranks a proposal ready slate, and carries the human approval workflow and the adverse impact
readout that a proposal can be defended with.</p></div>
<div class="card"><div class="k">missionMATCH™</div>
<strong>Who can support this mission today?</strong>
<p class="small" style="margin-top:6px">The workforce intelligence view. A command center that names the
staffing gaps, quantifies the revenue at risk, surfaces upcoming opportunities and the incumbent landscape,
and lets the whole team ask the AI brain a plain language question.</p></div>
<div class="card"><div class="k">recruitMATCH™</div>
<strong>Who is working the desk, and how is it going?</strong>
<p class="small" style="margin-top:6px">The delivery side. Clients, job orders and the hiring pipeline from
first contact to placement, with the money modelled properly: a wrap rate, a real cost per hour, and margin
reported separately from spread. Above it a manager view that scopes to a desk or a person, compares every
figure against the window before it, bands recruiter load against the published benchmark, and turns a
target into attainment.</p></div>
</div>
<h3>The loop they serve</h3>
<p>The four tools are stages of one loop. A requirement enters, candidate intelligence is gathered, the engine
scores the match, a ranked slate is produced, and proposal readiness is recorded. The output of each stage is the
input to the next, and every stage writes to the same audited system of record.</p>
<div style="text-align:center;margin:14px 0;">
<span class="pill navy">Requirement</span> →
<span class="pill steel">Candidate Intelligence</span> →
<span class="pill steel">Match Scoring</span> →
<span class="pill steel">Ranked Slate</span> →
<span class="pill gold">Proposal Readiness</span>
</div>
<div class="callout navy">
<strong>Why one loop matters.</strong> Because the tools share an engine and a data model, the command center
can name a gap and the candidates view can show the exact people who close it, telling one connected story
rather than three disconnected reports.
</div>
</section>
<!-- ============================ 04 HOW IT WORKS, STEP BY STEP ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>04 How it works</span></div>
<div class="sectiontag">Section 04</div>
<h2>How It Works, Step by Step</h2>
<p class="lead">Follow a single requirement through the platform, from intake to a defensible proposal decision.</p>
<div class="step"><div class="no">1</div><div class="b"><h4>Intake the requirement</h4>
<p>A requirement arrives, from a solicitation, a task order, or a capture plan. It carries a labor category, a
required clearance level and poly, mandatory and desired skills, certifications, required years, a place of
performance, and the customer agency. The platform stores it under the tenant, isolated from every other
tenant by construction.</p></div></div>
<div class="step"><div class="no">2</div><div class="b"><h4>Gather candidate intelligence</h4>
<p>Candidate profiles are ingested from resumes and connected systems. Parsing runs behind a provider
interface so that cleared resumes, which are controlled unclassified information, are processed by an
accredited or self hosted endpoint, never a consumer tool. Skills are resolved against a cleared skills
ontology so that a synonym or an adjacent skill still matches.</p></div></div>
<div class="step"><div class="no">3</div><div class="b"><h4>Score the match, transparently</h4>
<p>A pure, deterministic engine scores each candidate against the requirement across six weighted dimensions.
The math is exact decimal arithmetic, so the same inputs always produce the same score, which is what makes the
result auditable. Every score comes with a per dimension breakdown and a plain language rationale.</p></div></div>
<div class="step"><div class="no">4</div><div class="b"><h4>Rank the slate</h4>
<p>For a requirement, the engine scores the whole eligible pool, ranks it, and assigns readiness bands. A
learned re ranker can surface the candidates a reviewer is most likely to approve, but it only reorders, it
never changes a score or a band. The frozen engine remains the single source of the number.</p></div></div>
<div class="step"><div class="no gold">5</div><div class="b"><h4>Keep a human in the loop</h4>
<p>A person approves or rejects every slate member. The platform never auto rejects a candidate. Each decision
is recorded with its rationale, so the slate carries its own defense.</p></div></div>
<div class="step"><div class="no gold">6</div><div class="b"><h4>Prove readiness and measure impact</h4>
<p>The platform rolls the slate up into proposal readiness, and it computes selection rates and four fifths
ratios so the customer can run a bias audit. Demographic data never touches the score, it lives in a separate,
access controlled module used only for this reporting.</p></div></div>
<div class="step"><div class="no gold">7</div><div class="b"><h4>Fuse the market and ask the brain</h4>
<p>Around the loop, the platform fuses real federal signal, open solicitations, historical awards, and labor
rates, and exposes an AI brain that answers plain language questions grounded strictly in the tenant's own
data, always citing its evidence and refusing anything it cannot support.</p></div></div>
</section>
<!-- ============================ 05 DATA FLOW CHART ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>05 Data flow chart</span></div>
<div class="sectiontag">Section 05</div>
<h2>Platform Data Flow Chart</h2>
<p class="lead">How data moves from source, through the isolation and scoring layers, to a defensible decision and
an immutable audit trail.</p>
<svg viewBox="0 0 760 720" width="100%" style="font-family:Helvetica,Arial,sans-serif;">
<defs>
<marker id="arw" markerWidth="9" markerHeight="9" refX="7" refY="3" orient="auto" markerUnits="strokeWidth">
<path d="M0,0 L7,3 L0,6 Z" fill="#2E5EAA"/>
</marker>
<marker id="arwg" markerWidth="9" markerHeight="9" refX="7" refY="3" orient="auto" markerUnits="strokeWidth">
<path d="M0,0 L7,3 L0,6 Z" fill="#D4A017"/>
</marker>
</defs>
<!-- Row 1: sources -->
<text x="380" y="20" text-anchor="middle" font-size="12" font-weight="700" fill="#0F2744">SOURCES</text>
<g font-size="11" fill="#1a2331">
<rect x="20" y="30" width="150" height="46" rx="7" fill="#eef3fb" stroke="#2E5EAA"/>
<text x="95" y="50" text-anchor="middle" font-weight="700">Resumes and profiles</text>
<text x="95" y="66" text-anchor="middle" fill="#5b6b7f">controlled, parsed privately</text>
<rect x="190" y="30" width="150" height="46" rx="7" fill="#eef3fb" stroke="#2E5EAA"/>
<text x="265" y="50" text-anchor="middle" font-weight="700">Requirements</text>
<text x="265" y="66" text-anchor="middle" fill="#5b6b7f">solicitations, task orders</text>
<rect x="360" y="30" width="180" height="46" rx="7" fill="#eef3fb" stroke="#2E5EAA"/>
<text x="450" y="50" text-anchor="middle" font-weight="700">Federal market signal</text>
<text x="450" y="66" text-anchor="middle" fill="#5b6b7f">SAM opps, awards, labor rates</text>
<rect x="560" y="30" width="180" height="46" rx="7" fill="#eef3fb" stroke="#2E5EAA"/>
<text x="650" y="50" text-anchor="middle" font-weight="700">Connected systems</text>
<text x="650" y="66" text-anchor="middle" fill="#5b6b7f">applicant tracking, integration ready</text>
</g>
<line x1="95" y1="76" x2="95" y2="110" stroke="#2E5EAA" marker-end="url(#arw)"/>
<line x1="265" y1="76" x2="265" y2="110" stroke="#2E5EAA" marker-end="url(#arw)"/>
<line x1="450" y1="76" x2="450" y2="110" stroke="#2E5EAA" marker-end="url(#arw)"/>
<line x1="650" y1="76" x2="650" y2="110" stroke="#2E5EAA" marker-end="url(#arw)"/>
<!-- Row 2: ingestion + ontology -->
<rect x="20" y="112" width="720" height="58" rx="8" fill="#F4F6F8" stroke="#dfe5ec"/>
<text x="380" y="132" text-anchor="middle" font-size="12" font-weight="700" fill="#0F2744">INGESTION AND RESOLUTION</text>
<text x="380" y="152" text-anchor="middle" font-size="11" fill="#1a2331">Private parsing behind a provider interface, skills resolved against the cleared skills ontology, embeddings for hybrid search</text>
<line x1="380" y1="170" x2="380" y2="200" stroke="#2E5EAA" marker-end="url(#arw)"/>
<!-- Row 3: tenant isolation boundary -->
<rect x="20" y="202" width="720" height="70" rx="8" fill="#fff" stroke="#0F2744" stroke-width="2" stroke-dasharray="5 4"/>
<text x="380" y="222" text-anchor="middle" font-size="12" font-weight="700" fill="#0F2744">TENANT ISOLATION BOUNDARY</text>
<text x="380" y="242" text-anchor="middle" font-size="11" fill="#1a2331">Row level security on every table, composite keys carry the tenant, default deny when no tenant is set</text>
<text x="380" y="260" text-anchor="middle" font-size="10.5" fill="#5b6b7f">The application role can never bypass isolation. A separate schema holds demographics, unreachable from scoring.</text>
<line x1="380" y1="272" x2="380" y2="300" stroke="#2E5EAA" marker-end="url(#arw)"/>
<!-- Row 4: engine -->
<rect x="90" y="302" width="580" height="74" rx="8" fill="#0F2744"/>
<text x="380" y="324" text-anchor="middle" font-size="12" font-weight="700" fill="#fff">FROZEN DETERMINISTIC SCORING ENGINE</text>
<text x="380" y="344" text-anchor="middle" font-size="10.5" fill="#cfe0f5">Clearance .25 · Skills .25 · Certifications .15 · Customer experience .15 · Experience .10 · Location .10</text>
<text x="380" y="362" text-anchor="middle" font-size="10.5" fill="#D4A017">Exact decimal arithmetic, the single per candidate scorer, explainable and repeatable</text>
<line x1="380" y1="376" x2="380" y2="404" stroke="#2E5EAA" marker-end="url(#arw)"/>
<!-- Row 5: AI brain wraps -->
<rect x="20" y="406" width="720" height="60" rx="8" fill="#eef3fb" stroke="#2E5EAA"/>
<text x="380" y="426" text-anchor="middle" font-size="12" font-weight="700" fill="#0F2744">AI BRAIN, ON TOP OF THE ENGINE, NEVER AROUND IT</text>
<text x="380" y="446" text-anchor="middle" font-size="11" fill="#1a2331">Retrieval, table analytics, graph reasoning, and learned models, each a closed and validated intent, behind a faithfulness gate</text>
<line x1="380" y1="466" x2="380" y2="494" stroke="#D4A017" stroke-width="2" marker-end="url(#arwg)"/>
<!-- Row 6: outputs -->
<text x="380" y="486" text-anchor="middle" font-size="1" fill="#fff">.</text>
<g font-size="11" fill="#1a2331">
<rect x="40" y="496" width="200" height="52" rx="7" fill="#fdf7e8" stroke="#D4A017"/>
<text x="140" y="516" text-anchor="middle" font-weight="700">Explainable score and slate</text>
<text x="140" y="534" text-anchor="middle" fill="#5b6b7f">per dimension breakdown, bands</text>
<rect x="280" y="496" width="200" height="52" rx="7" fill="#fdf7e8" stroke="#D4A017"/>
<text x="380" y="516" text-anchor="middle" font-weight="700">Human decision, in the loop</text>
<text x="380" y="534" text-anchor="middle" fill="#5b6b7f">approve or reject, never auto reject</text>
<rect x="520" y="496" width="200" height="52" rx="7" fill="#fdf7e8" stroke="#D4A017"/>
<text x="620" y="516" text-anchor="middle" font-weight="700">Adverse impact reporting</text>
<text x="620" y="534" text-anchor="middle" fill="#5b6b7f">selection rates, four fifths ratios</text>
</g>
<line x1="140" y1="548" x2="140" y2="580" stroke="#2E5EAA" marker-end="url(#arw)"/>
<line x1="380" y1="548" x2="380" y2="580" stroke="#2E5EAA" marker-end="url(#arw)"/>
<line x1="620" y1="548" x2="620" y2="580" stroke="#2E5EAA" marker-end="url(#arw)"/>
<!-- Row 7: audit -->
<rect x="120" y="582" width="520" height="54" rx="8" fill="#0F2744"/>
<text x="380" y="604" text-anchor="middle" font-size="12" font-weight="700" fill="#fff">APPEND ONLY AUDIT AND DECISION TRACE</text>
<text x="380" y="623" text-anchor="middle" font-size="10.5" fill="#cfe0f5">Immutable, outside tenant policies, no protected attributes, the record a review runs on</text>
<!-- feedback loop -->
<path d="M120,609 C60,609 60,420 20,420" fill="none" stroke="#5b6b7f" stroke-dasharray="3 3"/>
<text x="35" y="670" font-size="9.5" fill="#5b6b7f">Decisions and outcomes feed the learning loop under strict fairness gates</text>
</svg>
</section>
<!-- ============================ 06 SCORING ENGINE ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>06 Scoring engine</span></div>
<div class="sectiontag">Section 06</div>
<h2>The Scoring Engine, Explainable by Design</h2>
<p class="lead">A pure, deterministic model is the floor of the whole platform. Everything else reads it and
narrates it, nothing replaces it.</p>
<table>
<thead><tr><th>Dimension</th><th class="num">Weight</th><th>How it scores</th></tr></thead>
<tbody>
<tr><td>Clearance</td><td class="num">25</td><td>Exact or higher than required scores full. A higher level satisfies a lower one, a lower level or an expired or unknown clearance scores zero. The hierarchy is encoded.</td></tr>
<tr><td>Skills</td><td class="num">25</td><td>Full when all required skills are met. Exact match first, then semantic similarity for synonyms and adjacent skills, always recording which candidate skill matched which requirement.</td></tr>
<tr><td>Certifications</td><td class="num">15</td><td>Required certifications present and current.</td></tr>
<tr><td>Customer experience</td><td class="num">15</td><td>Prior experience with the requirement's customer agency.</td></tr>
<tr><td>Experience</td><td class="num">10</td><td>Years of relevant experience against the required minimum.</td></tr>
<tr><td>Location and availability</td><td class="num">10</td><td>Place of performance fit and current availability to staff.</td></tr>
</tbody>
</table>
<h3>Readiness bands</h3>
<div class="grid3">
<div class="card"><span class="band b-green"></span><strong>Green, proposal ready</strong><div class="small" style="margin-top:4px">Score 90 and above. Ready to place on a proposal.</div></div>
<div class="card"><span class="band b-amber"></span><strong>Yellow, potential</strong><div class="small" style="margin-top:4px">Score 75 to 89. Viable with a gap to close.</div></div>
<div class="card"><span class="band b-red"></span><strong>Red, recruiting required</strong><div class="small" style="margin-top:4px">Below 75. A gap the team must source against.</div></div>
</div>
<div class="callout navy" style="margin-top:16px">
<strong>Why deterministic decimal arithmetic.</strong> The engine uses exact decimal math, never floating point.
The same inputs always yield the same score, to the digit. That bit stable repeatability is what lets a score
stand as a defensible record months later, and it is why the scoring model can be an asset in a compliance
review rather than a risk.
</div>
<h3>Explainability, built in</h3>
<ul>
<li>Every score carries a per dimension breakdown, so a reviewer sees exactly why a candidate landed where they did.</li>
<li>Every score carries a plain language rationale and a gap summary.</li>
<li>Every decision leaves a recordable trace, the raw material for an audit.</li>
<li>The engine is a pure function with no database and no side effects, exhaustively tested with golden and property tests. Any future learning layer sits on top of it, never in place of it.</li>
</ul>
</section>
<!-- ============================ 07 AI BRAIN ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>07 The AI brain</span></div>
<div class="sectiontag">Section 07</div>
<h2>The AI Brain, Four Augmentation Classes Over One Engine</h2>
<p class="lead">The brain answers plain language questions, but it is not a chatbot bolted onto a database. It is a
closed set of validated intents, each grounded, each audited, each unable to invent a number.</p>
<div class="grid2">
<div class="card"><div class="k">Retrieval augmentation</div>
Answers narrative questions strictly from the tenant's own documents and profiles, citing the evidence it
used. It narrates over retrieved records, it never scores.</div>
<div class="card"><div class="k">Table augmentation</div>
Answers questions that require the database to compute, a count, a sum, a distribution, by choosing from a
curated set of safe, parameterized, read only queries. The model never writes a query itself.</div>
<div class="card"><div class="k">Graph reasoning</div>
Walks the relational graph already in the database, the skill adjacency, the market and incumbent landscape,
the clearance lattice, returning a cited evidence path rather than an opinion.</div>
<div class="card"><div class="k">Model augmentation</div>
Serves calibrated learned signals, a win probability, a display order, a time to fill, computed from
interpretable coefficients. By construction these can only emit an opportunity level number or an ordering,
never a per candidate score.</div>
</div>
<h3>The guardrails that make it safe</h3>
<ul>
<li><strong>A closed registry.</strong> Every capability is a named, reviewed intent validated when the system starts. There is no free form path to the data.</li>
<li><strong>A faithfulness gate.</strong> Generated prose ships only when it is confirmed to be supported by the evidence. Otherwise the platform returns the deterministic rendering of the underlying data, never a confident guess.</li>
<li><strong>Refusal by design.</strong> A question about a protected attribute, or one the platform cannot ground, is refused, not answered.</li>
<li><strong>Small cell suppression.</strong> Any count derived from people is suppressed below a safe threshold so an answer can never re identify an individual.</li>
<li><strong>The engine stays the floor.</strong> No brain path recomputes or replaces the score. It reads what the engine decided and explains it.</li>
</ul>
<div class="callout">
<strong>What a user experiences.</strong> A capture lead types, who can support the intelligence analyst mission,
or, what are our hardest staffing gaps, and receives a grounded answer with its citations, in seconds, without
ever exposing a protected attribute or leaving the tenant boundary.
</div>
</section>
<!-- ============================ 08 ARCHITECTURE ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>08 Architecture</span></div>
<div class="sectiontag">Section 08</div>
<h2>Architecture and Technology</h2>
<p class="lead">Chosen for cloud portability, a clean federal security story, and long term maintainability.</p>
<div class="grid2">
<div class="card"><div class="k">Backend</div>
A single compiled, memory safe service in Go. One static binary, native validated cryptography, no heavy
runtime to accredit. Thin handlers, logic in services, typed and compile checked database access.</div>
<div class="card"><div class="k">Data</div>
PostgreSQL with a vector extension for semantic search. Hybrid retrieval fuses full text and vector search.
Schema changes only ever happen through reviewed migrations.</div>
<div class="card"><div class="k">Tenancy</div>
Postgres row level security in a pooled model. Every tenant scoped table enforces isolation with a using and
a with check policy and forced row level security. No tenant context means zero rows, a safe default.</div>
<div class="card"><div class="k">Frontend</div>
A modern typed single page application, a left navigation shell, stat cards, dashboards, and the four tool
surfaces, talking to the service over a first party authenticated session.</div>
</div>
<h3>The layered design</h3>
<table>
<thead><tr><th>Layer</th><th>Responsibility</th></tr></thead>
<tbody>
<tr><td>Platform</td><td>Cross cutting concerns, configuration, database, tenancy, security, audit, storage, and the embedding and parsing providers, each behind an interface.</td></tr>
<tr><td>Engine</td><td>The pure deterministic scoring model, no input or output, the single per candidate scorer.</td></tr>
<tr><td>Modules</td><td>Each domain, matching, slates, command center, opportunity intelligence, compliance, auth, and the AI brain, as a self contained unit.</td></tr>
<tr><td>Interface</td><td>The HTTP API and the typed frontend that consume the modules.</td></tr>
</tbody>
</table>
<h3>Portability, a founding requirement</h3>
<p>Everything cloud specific, object storage, the model provider, secrets, and identity, lives behind an
interface. The platform runs on Amazon Web Services GovCloud or Azure Government with the other cloud's adapter
present. Choosing a cloud is a configuration decision, not a code change, and there is no single vendor lock in
on the core path.</p>
<div class="callout navy">
<strong>Why Go and Postgres.</strong> The combination gives a single accreditable binary with validated
cryptography and a portable, managed database on either government cloud. It is the cleanest path to a federal
security posture without betting the product on one vendor's proprietary services.
</div>
</section>
<!-- ============================ 09 RESPONSIBLE AI / COMPLIANCE ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>09 Responsible AI</span></div>
<div class="sectiontag">Section 09</div>
<h2>Responsible AI, Compliance, and Auditability</h2>
<p class="lead">This is an Automated Employment Decision Tool, and it was designed from the first line to be
defensible under scrutiny.</p>
<div class="grid2">
<div class="card tint"><div class="k">Explainable</div>Every match score is a per dimension breakdown plus a human readable rationale plus a gap summary plus a recordable decision trace.</div>
<div class="card tint"><div class="k">Human in the loop</div>People approve or reject every slate member. The platform never automatically rejects a candidate.</div>
<div class="card tint"><div class="k">Demographics walled off</div>Protected attributes live in a separate, access controlled module. They are never an input to scoring, and the scoring code cannot reach them.</div>
<div class="card tint"><div class="k">Adverse impact reporting</div>The platform computes selection rates and four fifths ratios so a customer can run a NYC Local Law 144 or an OFCCP aligned review.</div>
</div>
<h3>How the firewall is enforced</h3>
<ul>
<li>Demographic data lives in its own database schema reachable only by a dedicated compliance role. The application scoring role has no access to it at all.</li>
<li>The AI brain refuses any question that references a protected attribute or a close proxy, in plain words or in a query.</li>
<li>Adverse impact is computed through the compliance path only, and reporting on people is suppressed below a safe cell size so it cannot re identify anyone.</li>
<li>Every scoring and decision event is written to an append only audit record that carries no protected attribute and cannot be altered by the application.</li>
</ul>
<div class="callout">
<strong>An important honesty.</strong> The platform provides the data a customer needs for their own bias audit.
It does not itself constitute the audit, and using it does not transfer the employer's legal responsibility. We
state this plainly because a serious federal buyer expects that clarity.
</div>
<div class="callout navy">
<strong>Clearance is intelligence, not verification.</strong> Clearance values in the platform are self reported
indicators shown as clearance intelligence. The authoritative check remains the hiring customer's facility
security officer through the government system of record at onboarding. The platform states this once wherever
clearance appears, so no one mistakes an indicator for a verification.
</div>
</section>
<!-- ============================ 10 SECURITY / DEPLOYMENT ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>10 Security and deployment</span></div>
<div class="sectiontag">Section 10</div>
<h2>Security and Deployment Posture</h2>
<p class="lead">Aligned to the federal control baseline, with validated cryptography enabled from day one.</p>
<div class="grid2">
<div class="card"><div class="k">Validated cryptography</div>
The service is built with the native validated cryptographic module enabled. Passwords use a standards based
key derivation with a high iteration count and a server held pepper. Secrets at rest are encrypted with
authenticated encryption, with versioned keys so they can rotate.</div>
<div class="card"><div class="k">Authentication</div>
First party opaque server side sessions in a hardened cookie, instantly revocable, with mandatory time based
one time password multifactor implemented on the validated standard library. No path yields an active
session with multifactor unsatisfied.</div>
<div class="card"><div class="k">Access and identity</div>
Role based access, one human to one account to one organization, provisioning and authority bounded invites
rather than open self signup, and federated single sign on kept behind a clean interface for when a customer
needs it.</div>
<div class="card"><div class="k">Data protection</div>
Controlled unclassified information is never logged. Cleared resumes are parsed by an accredited or self
hosted endpoint. Transport is encrypted, and every export is logged.</div>
</div>
<h3>Delivery</h3>
<ul>
<li>Delivered as containers with infrastructure as code, targeting both government clouds, with a software bill of materials produced at build.</li>
<li>Row level security, append only audit, and least privilege database roles are structural, not optional configuration.</li>
<li>A continuous integration gate fails closed on any attempt to reintroduce a development only bypass into a production build.</li>
</ul>
<div class="callout warn">
<strong>Accreditation is a shared journey.</strong> The platform is engineered to the federal baseline and uses
validated cryptography, which shortens the path. A specific authorization to operate in a customer environment
is a joint effort with the customer's security team, using the customer's accredited cloud and endpoints.
</div>
</section>
<!-- ============================ 11 COMMERCIAL BRIEF ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>11 Why we win</span></div>
<div class="sectiontag">Section 11</div>
<h2>Why We Win, the Commercial Brief</h2>
<p class="lead">The value is measured in bids won, hours saved, and audits passed.</p>
<h3>The value we create</h3>
<div class="grid3">
<div class="card"><div class="k">Win more</div>Stronger, faster, defensible slates. The command center names the gap and the platform shows the exact people who close it, before the proposal is due.</div>
<div class="card"><div class="k">Spend less effort</div>The hours a team burns fusing resumes, requirements, and market signal by hand collapse into a single scored view.</div>
<div class="card"><div class="k">Carry less risk</div>Every employment decision arrives with its own explanation and audit trail, and the adverse impact reporting a review needs.</div>
</div>
<h3>Who buys, and why</h3>
<table>
<thead><tr><th>Buyer</th><th>Their pain</th><th>What the platform gives them</th></tr></thead>
<tbody>
<tr><td>Capture and proposal teams</td><td>Slates assembled under deadline, on instinct</td><td>A ranked, proposal ready slate with a defensible rationale in minutes</td></tr>
<tr><td>Cleared staffing firms</td><td>Matching cleared talent to reqs at scale</td><td>A screening and slate engine that understands clearances natively</td></tr>
<tr><td>Program and workforce leads</td><td>No live picture of staffing gaps and risk</td><td>A command center that names gaps and quantifies revenue at risk</td></tr>
<tr><td>Compliance and legal</td><td>Exposure on automated employment decisions</td><td>Explainability, a human in the loop, and adverse impact reporting</td></tr>
</tbody>
</table>
<h3>Our defensible advantages</h3>
<div class="grid2">
<div class="card tint"><div class="k">Purpose built for cleared work</div>Clearance, poly, and compartment logic and controlled data handling are first class, not retrofitted onto a commercial applicant tracking system.</div>
<div class="card tint"><div class="k">Compliance as a moat</div>An explainable, auditable, firewall enforced decision tool is hard to copy and exactly what a regulated buyer requires.</div>
<div class="card tint"><div class="k">One engine, one story</div>Four tools over one engine and one data model tell a single connected story instead of four disconnected reports.</div>
<div class="card tint"><div class="k">Portable and future proof</div>Both government clouds, no lock in, and a learning layer that improves ranking over time without ever compromising the defensible core.</div>
</div>
</section>
<!-- ============================ 12 ROADMAP ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>12 Roadmap</span></div>
<div class="sectiontag">Section 12</div>
<h2>Roadmap and Integration Readiness</h2>
<p class="lead">The core loop is built and running. The next horizon deepens the intelligence and connects the
systems a customer already owns.</p>
<h3>Live today</h3>
<p>
<span class="pill">Explainable scoring engine</span>
<span class="pill">screenMATCH</span>
<span class="pill">slateMATCH</span>
<span class="pill">missionMATCH command center</span>
<span class="pill">AI brain, four augmentation classes</span>
<span class="pill">Capture readiness decision</span>
<span class="pill">Vendor intelligence</span>
<span class="pill">Adverse impact reporting</span>
<span class="pill">Multi tenant isolation</span>
<span class="pill">Validated cryptography and authentication</span>
<span class="pill">Federal market signal fusion</span>
</p>
<h3>Learning layer, advancing</h3>
<p>Calibrated win probability, a display order re ranker, and a time to fill forecast, each learned from the
tenant's own outcomes, each governed by a quality and a fairness gate before it is ever promoted, and none of
which can replace the deterministic per candidate score.</p>
<h3>Integration ready, activated with the customer</h3>
<p>The following connect a customer's existing systems and licensed data. Each is engineered and waiting only on
the customer's own credentials and grants, which is the honest status, not a limitation of the platform.</p>
<table>
<thead><tr><th>Integration</th><th>Activated by</th></tr></thead>
<tbody>
<tr><td>Applicant tracking system ingestion</td><td>The customer's system credentials and tenant grant</td></tr>
<tr><td>Human capital and document systems</td><td>The customer's tenant scoped access grant</td></tr>
<tr><td>Licensed opportunity intelligence feeds</td><td>The customer's data license</td></tr>
<tr><td>Production deployment to a government cloud</td><td>The customer's accredited cloud account</td></tr>
<tr><td>Self hosted accredited model endpoint</td><td>The customer's provisioned secure endpoint</td></tr>
</tbody>
</table>
<div class="callout navy">
<strong>The engagement model.</strong> A pilot begins on synthetic data to prove the loop and the workflow,
then connects the customer's own systems and deploys into the customer's accredited environment. The platform
is ready for that on day one.
</div>
</section>
<!-- ============================ 13 LEGAL / DISCLAIMERS ============================ -->
<section class="page">
<div class="page-head"><span class="brand">missionMATCH™</span><span>13 Legal notice</span></div>
<div class="sectiontag">Section 13</div>
<h2>Full Legal Notice and Disclaimers</h2>
<div class="legal">
<h3>1. Confidentiality</h3>
<p>This document and all information it contains are confidential and proprietary to the platform owner. It is
provided to the named recipient solely to evaluate a potential business relationship. The recipient shall not
disclose it to any third party except to its own professional advisors who have a need to know and who are
bound by confidentiality obligations at least as protective as those stated here, shall protect it with no less
than a reasonable degree of care, and shall return or destroy it on request. These obligations survive the
end of any discussions between the parties.</p>
<h3>2. Intellectual property, reservation of rights</h3>
<p>The platform, its architecture, its scoring methodology, its data flows, its user interfaces, its
documentation, and the names missionMATCH, slateMATCH, and screenMATCH, together with all associated designs,
know how, and trade secrets, are the exclusive intellectual property of the platform owner and are protected by
applicable trade secret, copyright, trademark, and other laws. All rights are reserved.</p>
<h3>3. No license and no transfer</h3>
<p>Nothing in this document grants, by implication, estoppel, or otherwise, any license or right to any
patent, copyright, trademark, trade secret, or other intellectual property of the platform owner. No right to
make, use, reproduce, modify, distribute, reverse engineer, or create derivative works of the platform or any
part of it is conveyed. The recipient shall not use any concept, method, diagram, workflow, or design element
disclosed here to design, build, specify, procure, or assist a third party in building a competing or similar
capability.</p>
<h3>4. No warranty</h3>
<p>This material is provided for informational purposes only, on an as is basis, without warranty of any kind,
express or implied, including any warranty of merchantability, fitness for a particular purpose, accuracy, or
non infringement. Statements about capabilities, roadmap, and performance are forward looking and subject to
change without notice, and are not a commitment, guarantee, or contract.</p>
<h3>5. Demonstration and sample data</h3>
<p>Any candidate, personnel, clearance, opportunity, award, vendor, or organization data shown in a
demonstration or in this material is synthetic sample data generated for illustration. It does not represent
real individuals or real clearance determinations. Clearance indicators in the platform are self reported and
are presented as clearance intelligence, not as verification. The authoritative clearance determination is made
by the hiring customer's facility security officer through the government system of record at onboarding.</p>
<h3>6. Responsible use and no legal advice</h3>
<p>The platform is an aid to human decision making. It is designed to keep a qualified human in the loop for
every employment decision and it never automatically rejects a candidate. It provides data to support a
customer's own bias and compliance audits, but it does not itself constitute a legal audit, a compliance
certification, or legal advice, and its use does not transfer or discharge the employer's legal
responsibilities under applicable employment, civil rights, or contracting law. The customer remains
responsible for its own compliance obligations.</p>
<h3>7. Third party marks</h3>
<p>Any third party names, cloud provider names, agency names, or standards referenced are the property of their
respective owners and are used for identification only. Their use does not imply endorsement, affiliation, or
sponsorship.</p>
<h3>8. Acknowledgement</h3>
<p>By reviewing this document the recipient acknowledges and agrees to the terms of this notice. If the
recipient does not agree, the recipient must not review, copy, or use this document and must return or destroy
all copies.</p>
<p style="margin-top:16px;color:#0F2744;font-weight:700">Confidential and Proprietary. All rights reserved. Not for redistribution.</p>
</div>
</section>
</body>
</html>