danny/hosted
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ifttt: add constitutional "for whom" framing

Browse source
This commit is contained in:
root 2025-12-29 03:58:29 +00:00
parent 7b0d99c4de
commit 5a163a5ddc
2 changed files with 69 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
ifttt/fr/governance/index.html
View file

@ -101,6 +101,40 @@
</aside>
</div>
</section>
<section class="section">
<div class="wrap">
<h2>Pour qui (et qui va détester)</h2>
<p class="sub">Lisible pour des tiers : le but n’est pas le confort interne, mais la vérifiabilité externe.</p>
<div class="grid2">
<div class="panel">
<h3>Pour</h3>
<ul class="list">
<li><strong>GRC / audit</strong> (SOC 2 / ISO) : preuves exportables.</li>
<li><strong>Architecture sécurité</strong> : contrôles mesurables, pas d’attestations.</li>
<li><strong>Juridique / conformité</strong> : chaîne de possession en cas de litige.</li>
<li><strong>Produits IA</strong> : “pourquoi le modèle a dit ça ?”</li>
<li><strong>Secteur public / défense</strong> : vérification hors‑ligne et environnements verrouillés.</li>
</ul>
</div>
<div class="panel">
<h3>Pas pour</h3>
<ul class="list">
<li>Ceux qui veulent un “badge” sans publier d’artefacts vérifiables.</li>
<li>Les workflows où rien ne peut sortir du réseau (pas de surface publique).</li>
<li>Les organisations qui préfèrent l’ambiguïté : IF.TTT rend les trous visibles.</li>
</ul>
</div>
</div>
<div class="cta" style="margin-top: 12px">
<a class="btn btn--primary" href="../../whitepaper/">Lire le livre blanc</a>
<a class="btn" href="../../verticals/">Voir les verticaux</a>
</div>
</div>
</section>
</main>
<footer class="footer">

35
ifttt/governance/index.html
View file

@ -107,6 +107,41 @@
</div>
</section>
<section class="section">
<div class="wrap">
<h2>For whom (and who will hate it)</h2>
<p class="sub">A constitutional framing: the goal is legibility to outsiders, not internal comfort.</p>
<div class="grid2">
<div class="panel">
<h3>For</h3>
<ul class="list">
<li><strong>GRC / Audit leads</strong> drowning in evidence requests (SOC 2 / ISO 27001 / vendor due diligence).</li>
<li><strong>Security architects</strong> who need “proof of what ran” without adding manual theater.</li>
<li><strong>Legal / compliance</strong> teams who need chain‑of‑custody that survives disputes.</li>
<li><strong>AI product teams</strong> facing “why did it say that?” questions from customers and regulators.</li>
<li><strong>Gov/defense contractors</strong> who must verify artifacts offline or across locked‑down environments.</li>
</ul>
</div>
<div class="panel">
<h3>Not for</h3>
<ul class="list">
<li>Teams seeking a “compliance badge” without publishing verifiable artifacts.</li>
<li>Workflows where evidence cannot leave the internal network (no share surface, no external verification).</li>
<li>Organizations that want to hide uncertainty: IF.TTT makes gaps visible by design.</li>
<li>Anyone who needs governance to remain ambiguous (receipts reduce wiggle room).</li>
</ul>
</div>
</div>
<div class="cta" style="margin-top: 12px">
<a class="btn btn--primary" href="../whitepaper/">Read the paper</a>
<a class="btn" href="../verticals/">Browse vertical fit</a>
</div>
</div>
</section>
<section class="section section--alt">
<div class="wrap">
<h2>Charters (how we keep it honest)</h2>