Put the executive summary on page 2, before the table of contents.
Some checks are pending
ci / markdown (push) Waiting to run

The cover stays page 1. Numbered chapters now start at What Verae
provides. The TOC lists Executive summary at page 2.
This commit is contained in:
George Lambert 2026-09-16 01:21:05 -04:00
parent 5df7ed87d5
commit 8496ef8338
23 changed files with 759 additions and 723 deletions

View file

@ -5,19 +5,19 @@
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>16. George Lambert &#8212; Making yourself audit-ready with Verae DataCubes</title>
<title>15. George Lambert &#8212; Making yourself audit-ready with Verae DataCubes</title>
<link rel="stylesheet" type="text/css" href="_static/pygments.css?v=5ecbeea2" />
<link rel="stylesheet" type="text/css" href="_static/basic.css?v=b08954a9" />
<link rel="stylesheet" type="text/css" href="_static/alabaster.css?v=2a97f0c7" />
<link rel="stylesheet" type="text/css" href="_static/verae.css?v=050b9d5b" />
<link rel="stylesheet" type="text/css" href="_static/verae.css?v=2d7b7068" />
<script src="_static/documentation_options.js?v=250a654d"></script>
<script src="_static/doctools.js?v=fd6eb6e6"></script>
<script src="_static/sphinx_highlight.js?v=6ffebe34"></script>
<link rel="icon" href="_static/VeraeFullLogo.png"/>
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="17. Verae Inc — contact" href="contact.html" />
<link rel="prev" title="15. Stuart Haber" href="bio-stuart-haber.html" />
<link rel="next" title="16. Verae Inc — contact" href="contact.html" />
<link rel="prev" title="14. Stuart Haber" href="bio-stuart-haber.html" />
<link rel="stylesheet" href="_static/custom.css" type="text/css" />
@ -61,37 +61,36 @@
<script>document.getElementById('searchbox').style.display = "block"</script><h3>Navigation</h3>
<p class="caption" role="heading"><span class="caption-text">Contents</span></p>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="executive.html">1. Executive summary</a></li>
<li class="toctree-l1"><a class="reference internal" href="what-verae-provides.html">2. What Verae provides — and what it does not</a></li>
<li class="toctree-l1"><a class="reference internal" href="datacube-server.html">3. The Verae DataCube Server Solution</a></li>
<li class="toctree-l1"><a class="reference internal" href="data-in-transit.html">4. Secure communications — data in transit</a></li>
<li class="toctree-l1"><a class="reference internal" href="data-at-rest.html">5. Encryption at rest — IPFS blocks and Peergos</a></li>
<li class="toctree-l1"><a class="reference internal" href="timestamped-receipts.html">6. Global timestamped receipts</a></li>
<li class="toctree-l1"><a class="reference internal" href="peergos-eu-evaluations.html">7. Peergos security evaluations in Europe</a></li>
<li class="toctree-l1"><a class="reference internal" href="global-timestamping.html">8. Verae global timestamping — a cross-blockchain receipt</a></li>
<li class="toctree-l1"><a class="reference internal" href="iceberg-archive.html">9. Write-once Iceberg archive</a></li>
<li class="toctree-l1"><a class="reference internal" href="architecture.html">10. Architecture for an audit interview</a></li>
<li class="toctree-l1"><a class="reference internal" href="baa-dpa.html">11. BAAs, DPAs, and ciphertext without host keys</a></li>
<li class="toctree-l1"><a class="reference internal" href="checklist.html">12. Audit-ready checklist</a></li>
<li class="toctree-l1"><a class="reference internal" href="howto.html">13. How to use this briefing</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-james-garfinkel.html">14. James H. Garfinkel</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-stuart-haber.html">15. Stuart Haber</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="#">16. George Lambert</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#role">16.1. Role</a></li>
<li class="toctree-l2"><a class="reference internal" href="#internet-technical-architect-from-1994">16.2. Internet technical architect, from 1994</a></li>
<li class="toctree-l2"><a class="reference internal" href="#new-hampshire-public-office">16.3. New Hampshire public office</a></li>
<li class="toctree-l2"><a class="reference internal" href="#why-this-biography-is-in-the-briefing">16.4. Why this biography is in the briefing</a></li>
<li class="toctree-l1"><a class="reference internal" href="what-verae-provides.html">1. What Verae provides — and what it does not</a></li>
<li class="toctree-l1"><a class="reference internal" href="datacube-server.html">2. The Verae DataCube Server Solution</a></li>
<li class="toctree-l1"><a class="reference internal" href="data-in-transit.html">3. Secure communications — data in transit</a></li>
<li class="toctree-l1"><a class="reference internal" href="data-at-rest.html">4. Encryption at rest — IPFS blocks and Peergos</a></li>
<li class="toctree-l1"><a class="reference internal" href="timestamped-receipts.html">5. Global timestamped receipts</a></li>
<li class="toctree-l1"><a class="reference internal" href="peergos-eu-evaluations.html">6. Peergos security evaluations in Europe</a></li>
<li class="toctree-l1"><a class="reference internal" href="global-timestamping.html">7. Verae global timestamping — a cross-blockchain receipt</a></li>
<li class="toctree-l1"><a class="reference internal" href="iceberg-archive.html">8. Write-once Iceberg archive</a></li>
<li class="toctree-l1"><a class="reference internal" href="architecture.html">9. Architecture for an audit interview</a></li>
<li class="toctree-l1"><a class="reference internal" href="baa-dpa.html">10. BAAs, DPAs, and ciphertext without host keys</a></li>
<li class="toctree-l1"><a class="reference internal" href="checklist.html">11. Audit-ready checklist</a></li>
<li class="toctree-l1"><a class="reference internal" href="howto.html">12. How to use this briefing</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-james-garfinkel.html">13. James H. Garfinkel</a></li>
<li class="toctree-l1"><a class="reference internal" href="bio-stuart-haber.html">14. Stuart Haber</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="#">15. George Lambert</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#role">15.1. Role</a></li>
<li class="toctree-l2"><a class="reference internal" href="#internet-technical-architect-from-1994">15.2. Internet technical architect, from 1994</a></li>
<li class="toctree-l2"><a class="reference internal" href="#new-hampshire-public-office">15.3. New Hampshire public office</a></li>
<li class="toctree-l2"><a class="reference internal" href="#why-this-biography-is-in-the-briefing">15.4. Why this biography is in the briefing</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="contact.html">17. Verae Inc — contact</a></li>
<li class="toctree-l1"><a class="reference internal" href="contact.html">16. Verae Inc — contact</a></li>
</ul>
<div class="relations">
<h3>Related Topics</h3>
<ul>
<li><a href="index.html">Documentation overview</a><ul>
<li>Previous: <a href="bio-stuart-haber.html" title="previous chapter"><span class="section-number">15. </span>Stuart Haber</a></li>
<li>Next: <a href="contact.html" title="next chapter"><span class="section-number">17. </span>Verae Inc — contact</a></li>
<li>Previous: <a href="bio-stuart-haber.html" title="previous chapter"><span class="section-number">14. </span>Stuart Haber</a></li>
<li>Next: <a href="contact.html" title="next chapter"><span class="section-number">16. </span>Verae Inc — contact</a></li>
</ul></li>
</ul>
</div>
@ -112,9 +111,9 @@
<div class="body" role="main">
<section id="george-lambert">
<h1><span class="section-number">16. </span>George Lambert<a class="headerlink" href="#george-lambert" title="Link to this heading"></a></h1>
<h1><span class="section-number">15. </span>George Lambert<a class="headerlink" href="#george-lambert" title="Link to this heading"></a></h1>
<section id="role">
<h2><span class="section-number">16.1. </span>Role<a class="headerlink" href="#role" title="Link to this heading"></a></h2>
<h2><span class="section-number">15.1. </span>Role<a class="headerlink" href="#role" title="Link to this heading"></a></h2>
<p><strong>George Lambert</strong> is an Internet technical architect and a
New Hampshire public official. Public candidate listings
(BallotReady) identify him as <strong>CTO / Chief Architect, Verae
@ -125,7 +124,7 @@ public-key directory, organizational timestamping link, and
write-once archive that an organization actually runs.</p>
</section>
<section id="internet-technical-architect-from-1994">
<h2><span class="section-number">16.2. </span>Internet technical architect, from 1994<a class="headerlink" href="#internet-technical-architect-from-1994" title="Link to this heading"></a></h2>
<h2><span class="section-number">15.2. </span>Internet technical architect, from 1994<a class="headerlink" href="#internet-technical-architect-from-1994" title="Link to this heading"></a></h2>
<p>Lamberts public account of his engineering work begins in
the <strong>earliest days of the commercial Internet</strong>, when
shipping an application that could speak TCP/IP was still a
@ -156,7 +155,7 @@ systems, and later as founder of PodKey Solutions
(20042010) and as an interim/contract CTO.</p>
</section>
<section id="new-hampshire-public-office">
<h2><span class="section-number">16.3. </span>New Hampshire public office<a class="headerlink" href="#new-hampshire-public-office" title="Link to this heading"></a></h2>
<h2><span class="section-number">15.3. </span>New Hampshire public office<a class="headerlink" href="#new-hampshire-public-office" title="Link to this heading"></a></h2>
<p>Lambert is a <strong>Republican</strong> from <strong>Litchfield, New
Hampshire</strong>, born <strong>4 September 1968</strong> in Sanford, Maine
(Wikipedia; Vote Smart).</p>
@ -183,7 +182,7 @@ Borland fact as the credential for knowing what scalable
architecture looks like.</p>
</section>
<section id="why-this-biography-is-in-the-briefing">
<h2><span class="section-number">16.4. </span>Why this biography is in the briefing<a class="headerlink" href="#why-this-biography-is-in-the-briefing" title="Link to this heading"></a></h2>
<h2><span class="section-number">15.4. </span>Why this biography is in the briefing<a class="headerlink" href="#why-this-biography-is-in-the-briefing" title="Link to this heading"></a></h2>
<p>The DataCube Server Solution is not only a timestamping
API. It is a <strong>running system</strong>: keys, brokers, cryptree,
replicas, admin-history, Iceberg export. Lambert is the