sf-smartpangolin 3.0.0__tar.gz

sf_smartpangolin-3.0.0/.gitignore

@@ -0,0 +1,57 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+# NOTE: this project ships a real `build/` content folder (build-all scripts) and
+# builds with hatchling (output goes to dist/), so we do NOT ignore build/.
+dist/
+.venv/
+venv/
+ft-venv/
+env/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+# SmartPangolin's own generated artifacts live one level up, but ignore them if run in-tree:
+extracted_source/
+share_archive/
+file_folder_tree.txt
+file_folder_path.txt
+# Never commit real secrets:
+.env
+.secret/
+!.secret/.gitignore
+# ...except the intentional demo fixture that the scanner demo relies on:
+!demo/repo/.env
+
+# secrets and credentials never belong in the repository
+.secure/
+secrets.env
+*.env
+.env.*
+!.env.example
+.npmrc
+.pypirc
+.netrc
+_netrc
+id_rsa*
+id_ed25519*
+*.key
+*.pem
+*.p12
+*.pfx
+
+# port build output
+*.class
+ports/java/out/
+ports/go/pangolin-check
+ports/go/pangolincheck
+
+# test and demo fixtures (fake values) that are tracked on purpose
+!demo/repo/.env
+!demo/repo/deploy/id_rsa
+
+# binary from `go build` in ports/go (the module path ends in /go)
+ports/go/go

sf_smartpangolin-3.0.0/CHANGELOG.md

@@ -0,0 +1,69 @@
+# Changelog
+
+All notable changes to SmartPangolin are documented here. Format follows
+[Keep a Changelog](https://keepachangelog.com/); versioning is semantic.
+
+## Unreleased
+
+### Security
+- Install instructions no longer name packages the maintainers have not
+  published. Until the first release, install from a clone (README, "Install").
+- New `SECURITY.md` (private vulnerability reporting), `names.json` (the only
+  official package names) and a CI check that fails when a document names any
+  other package.
+- Releases are built and published only by `.github/workflows/release.yml`
+  through PyPI trusted publishing, with provenance attestations.
+
+### Changed
+- **Renamed (breaking), `sf-` = Smart Family:** repository `SmartTasksOrg/sf-smartpangolin`, PyPI package `sf-smartpangolin`, command `sf-smartpangolin`, import package `sf_smartpangolin`, MCP server `io.github.smarttasksorg/sf-smartpangolin`. The unprefixed names are not used any more, so nobody can be sent to a look-alike.
+- README: "Install" and "Status" sections (Status: experimental, no "production" claim); MCP marker is the bare server name.
+- `pyproject.toml`: "3 - Alpha" classifier (was "5 - Production/Stable"), licence files incl. NOTICE, URLs point at `master`.
+- Token uploads removed: `make publish`, `make publish-test` and `scripts/publish.sh` no longer upload; `PUBLISHING.md` rewritten.
+- Docs refer to tag `v3.0.0` (the first release) instead of `v1.0.0`/`v1`, which do not exist.
+- Node port package `sf-smartpangolin-check` (unpublished); Go module path `github.com/SmartTasksOrg/sf-smartpangolin/ports/go`.
+- `MARKETING.md` moved out of the public repository.
+
+## [3.0.0] — 2026-08-04
+
+Aligned to the **Smart\* family v3.0.0** release. The full packager (`pango`
+`pack`/`verify`/`triage`, engine, PII, ports, kits, adapters, docs) is unchanged
+and intact. Additions for family integration:
+
+- Family quick-scan API — `smartpangolin.core.scan()` and `smartpangolin.models`
+  (`ScanResult`, `Finding`) — with **base64/hex-decode-aware** secret detection and
+  a **deterministic, real SHA-256** `policy_hash`.
+- Bundled `demo/repo`, IAIso mapping (`spec/iaiso-map.json`), `.smart.json` family
+  metadata, and a `smartpangolin` console alias (the `pango` command is unchanged).
+- `pango`/`smartpangolin` (no args) and `--demo` now run a safe demo instead of
+  packing the current directory.
+
+## [1.0.0] — 2026-08-02
+
+First public release. Extracted and hardened from the SmartTasks internal
+`get_folder_structure.py -> get_source.py -> get_share_zip.py` pipeline.
+
+### Added
+- `pango` CLI (`pack`, `verify`, `triage`, `tree`, `purge`, `policy`, `init`) and
+  a Python API `smartpangolin.pack()` returning a structured `PackResult`.
+- Rule families with stable, greppable IDs recorded in `EXCLUSIONS.json`:
+  `SEC-PATH-*` (dangerous filenames), `SEC-CONT-*` (~20 in-content secret
+  patterns), `LOC-*` (local-infrastructure leaks), `OPS-*` (operational).
+- `.gitignore` honouring (`OPS-GITIGNORE`) — nested files, negation, anchored and
+  directory patterns, `**`; on by default, overridable and auditable.
+- `public` / `private` share modes (local-infrastructure disclosure toggle).
+- The `.secret/` folder standard (`SEC-DIR-SECRET`) and per-repo `.pangolin.json`
+  overrides that fold into an auditable `policy_sha256`; deterministic
+  `content_sha256` and byte-reproducible archives.
+- Native, dependency-free ports for **Node, Go, Java, and PHP**, each conformance-
+  tested to produce the same rule IDs as the Python reference on every rule and
+  both share modes (`ports/conformance/run.sh`).
+- Integration kits: a zero-dependency **MCP server** (`smartpangolin-mcp`) for AI
+  coding tools, plus LangChain / LlamaIndex / function-calling adapters and
+  CI / pre-commit templates.
+- Editor secret-search patterns for VS Code and ripgrep, and a one-command
+  bootstrap for the standardized secret locations.
+- Hardening: secrets embedded in binary-safe assets (images, fonts) and in
+  oversize files are now scanned and withheld, and zero-width / invisible
+  characters are stripped before matching (so a key split by a hidden character
+  is still caught) — across Python and all four ports.
+

sf_smartpangolin-3.0.0/LICENSE

@@ -0,0 +1,200 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but not
+      limited to compiled object code, generated documentation, and
+      conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work.
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including the
+      original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and do
+          not modify the License. You may add Your own attribution notices
+          within Derivative Works that You distribute, alongside or as an
+          addendum to the NOTICE text from the Work, provided that such
+          additional attribution notices cannot be construed as modifying
+          the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

sf_smartpangolin-3.0.0/NOTICE

@@ -0,0 +1,16 @@
+SmartPangolin
+Copyright 2026 Roen Branham, Le Thanh
+
+Licensed under the Apache License, Version 2.0 (see LICENSE).
+
+Names and affiliation
+---------------------
+
+SmartPangolin is published by SmartTasksOrg. The only package names it is
+published under are those marked "registered": true in names.json.
+
+LangChain is a trademark of its owner.
+LlamaIndex is a trademark of its owner.
+All other names are the property of their respective owners. Their use here
+only says what the software reads, evaluates or connects to; it does not
+imply affiliation, sponsorship or endorsement.

sf_smartpangolin-3.0.0/PKG-INFO

@@ -0,0 +1,279 @@
+Metadata-Version: 2.5
+Name: sf-smartpangolin
+Version: 3.0.0
+Summary: Deterministic, fail-closed, auditable secret-scrubbing packager for sharing code and data with LLMs and third parties.
+Project-URL: Homepage, https://github.com/SmartTasksOrg/sf-smartpangolin
+Project-URL: Source, https://github.com/SmartTasksOrg/sf-smartpangolin
+Project-URL: Issues, https://github.com/SmartTasksOrg/sf-smartpangolin/issues
+Project-URL: Security, https://github.com/SmartTasksOrg/sf-smartpangolin/security/policy
+Project-URL: Changelog, https://github.com/SmartTasksOrg/sf-smartpangolin/blob/master/CHANGELOG.md
+Project-URL: Documentation, https://github.com/SmartTasksOrg/sf-smartpangolin/tree/master/docs
+Project-URL: SmartTasks (data fabric), https://smarttasks.cloud
+Project-URL: IAIso (control framework), https://iaiso.org
+Project-URL: Model repacks (Hugging Face), https://huggingface.co/smarttasks
+Author: Roen Branham, Le Thanh
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: context,deterministic,iaiso,llm,pre-commit,provenance,redaction,sbom,secrets,security,share,smarttasks,supply-chain
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Information Technology
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Utilities
+Requires-Python: >=3.8
+Provides-Extra: dev
+Requires-Dist: build>=1.0; extra == 'dev'
+Requires-Dist: pytest>=7; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Requires-Dist: twine>=5.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+<!-- mcp-name: io.github.smarttasksorg/sf-smartpangolin -->
+<h1 align="center">🦔 SmartPangolin</h1>
+<p align="center"><b>Scan before you share. Stop leaking secrets into AI models, agents, and tools.</b></p>
+<p align="center">
+  <a href="https://iaiso.org">IAIso §1 · Secure Sharing</a> ·
+  <a href="https://smarttasks.cloud">SmartTasks.cloud</a> ·
+  <a href="#part-of-the-smart-family">the Smart* family</a>
+</p>
+
+---
+
+## You paste your repo into an AI. What did you just leak?
+
+As AI reshapes how we work, a new gap opens: feeding code/docs to ai leaks secrets, keys, and internal detail. **SmartPangolin** closes it —
+`scan` at the exact moment the gap bites, and it works the second you clone it
+(a synthetic demo ships in `demo/`).
+
+## Install
+
+SmartPangolin is not published on PyPI or any other package registry yet. Until
+this section says otherwise, a package called `sf-smartpangolin` on any registry
+is not ours, and neither is `smartpangolin`. The PyPI package `pango` is a placeholder published by someone else; it is not this tool.
+
+Install from a clone (Python 3.8 or later):
+
+```bash
+git clone https://github.com/SmartTasksOrg/sf-smartpangolin
+cd sf-smartpangolin
+python -m venv .venv
+. .venv/bin/activate          # Windows PowerShell: .\.venv\Scripts\Activate.ps1
+python -m pip install .
+sf-smartpangolin --demo
+```
+
+## Status
+
+- **Version 3.0.0, experimental.** A deterministic secret-scanning packager with 31 tests, including red-team regression cases; [SECURITY.md](SECURITY.md#detection-scope--limitations-be-honest-with-yourself) lists what it does not detect.
+- **Published:** nowhere yet; install from a clone (above).
+- **Tested:** lint, the 31 tests and a `sf-smartpangolin pack` dry run on Linux, Windows and macOS with Python 3.8, 3.10 and 3.12, on every push to master and every pull request (`.github/workflows/ci.yml`).
+- **Not tested:** Python 3.9, 3.11 and 3.13.
+- **Ports:** Go, Java, Node and PHP ports in `ports/` are checked against the Python reference by `ports/conformance/run.sh` (run by hand, not in CI); they are not published on any registry.
+- **Security review:** none independent. Report vulnerabilities as described in [SECURITY.md](SECURITY.md).
+
+## Run it in your stack
+
+| Where you work | How you run it |
+|---|---|
+| **Python** | from a clone: `python -m pip install .` (not on PyPI yet) |
+| **Go · Java · Node · PHP** | native ports in [`ports/`](ports/), each verified against the Python reference by [`ports/conformance/run.sh`](ports/conformance/run.sh) |
+| **LangChain · LlamaIndex · function-calling · MCP** | drop-in integration kits in [`kits/`](kits/) |
+| **Flowise · VS Code** | ready-made wrappers in [`integrations/`](integrations/), all calling one `adapter.py` |
+| **CI / pre-commit** | add the hook from [`.pre-commit-hooks.yaml`](.pre-commit-hooks.yaml) |
+
+## What's in this repo
+
+- **Core engine** — [`src/sf_smartpangolin/`](src/sf_smartpangolin/): scan() -> ScanResult. Deterministic, dependency-free.
+- **CLI** — `sf-smartpangolin pack | verify | triage | tree | purge | policy | init`, the full fail-closed packager. `sf-smartpangolin --demo` runs the quick demo; the family `scan()` API is the lightweight scanner.
+- **Language ports** — [`ports/`](ports/): native Go, Java, Node, PHP implementations that reproduce the Python reference, with a shared conformance harness.
+- **Integration kits** — [`kits/`](kits/): LangChain, LlamaIndex, function-calling, MCP, CI, and pre-commit starters.
+- **Adapters** — [`adapters/`](adapters/): GitHub Action and language adapters.
+- **Framework integrations** — [`integrations/`](integrations/): Flowise, VS Code extension — each a thin wrapper over one `adapter.py` bound to the core.
+- **MCP server** — `sf-smartpangolin-mcp` console script, for agentic/AI-coding clients.
+- **Reference docs** — [`docs/`](docs/): 10 documents (CLI, policy, design, FAQ, porting…).
+- **Also included** — a runnable [`demo/`](demo/), [`examples/`](examples/), the IAIso mapping [`spec/iaiso-map.json`](spec/iaiso-map.json), a browser [`site/playground.html`](site/playground.html), plus public smoke tests in `tests/`.
+
+## How it works
+
+Rule IDs are namespaced `SEC-*` so output looks kin to the rest of the family
+(SmartCheck's `CHECK-*`, SmartSeal's `SEAL-*`, etc.). Deterministic, dependency-free, fail-loud.
+
+### The data objects (UML)
+
+These are real dataclasses in [`src/sf_smartpangolin/models.py`](src/sf_smartpangolin/models.py) — the
+diagram and the code are the same thing:
+
+```mermaid
+classDiagram
+    class Finding {
+      +rule: str
+      +severity: str
+      +path: str
+      +detail: str
+    }
+    class Policy {
+      +rules: list[str]
+      +hash: str
+    }
+    class ScanResult {
+      +findings: list[Finding]
+      +verdict: str
+      +policy_hash: str
+    }
+    class IAIsoControl {
+      +section: str
+      +name: str
+    }
+    ScanResult ..> IAIsoControl : conforms to
+```
+
+## Where it sits in the architecture
+
+SmartPangolin doesn't stand alone — it stacks with the family, and everything conforms to
+the IAIso standard — the same standard that governs SmartTasks' own apps, while each tool here stays standalone and drops into your architecture:
+
+```mermaid
+graph LR
+    IAIso([IAIso standard]):::std
+    Cloud([SmartTasks.cloud]):::cloud
+    SmartPangolin[SmartPangolin]:::tool
+    SmartPrompt[SmartPrompt]:::tool
+    SmartCheck[SmartCheck]:::tool
+    SmartSeal[SmartSeal]:::tool
+    SmartStandard[SmartStandard]:::tool
+    SmartSim[SmartSim]:::tool
+    SmartMoat[SmartMoat]:::tool
+    SmartRoute[SmartRoute]:::tool
+    SmartFeed[SmartFeed]:::tool
+    SmartPangolin -->|emits clean artifacts to| SmartSeal
+    SmartPrompt -->|hands secret/PII flags to| SmartPangolin
+    SmartPrompt -->|enforces prompt rules from| SmartStandard
+    SmartCheck -->|stamps verified output with| SmartSeal
+    SmartCheck -->|checks against rules from| SmartStandard
+    SmartSeal -->|issues receipts consumed by| SmartCheck
+    SmartSeal -->|issues receipts consumed by| SmartRoute
+    SmartStandard -->|supplies rule sets to| SmartPrompt
+    SmartStandard -->|supplies rule sets to| SmartCheck
+    SmartSim -->|feeds role forecasts to| SmartMoat
+    SmartSim -->|draws signals from| SmartFeed
+    SmartMoat -->|consumes forecasts from| SmartSim
+    SmartRoute -->|verifies receipts from| SmartSeal
+    SmartRoute -->|enforces the standard from| SmartStandard
+    SmartFeed -->|feeds signals to| SmartSim
+    SmartFeed -->|feeds signals to| SmartMoat
+    SmartPangolin -.conforms.-> IAIso
+    SmartPangolin -.shares IAIso with.-> Cloud
+    SmartPrompt -.conforms.-> IAIso
+    SmartPrompt -.shares IAIso with.-> Cloud
+    SmartCheck -.conforms.-> IAIso
+    SmartCheck -.shares IAIso with.-> Cloud
+    SmartSeal -.conforms.-> IAIso
+    SmartSeal -.shares IAIso with.-> Cloud
+    SmartStandard -.conforms.-> IAIso
+    SmartStandard -.shares IAIso with.-> Cloud
+    SmartSim -.conforms.-> IAIso
+    SmartSim -.shares IAIso with.-> Cloud
+    SmartMoat -.conforms.-> IAIso
+    SmartMoat -.shares IAIso with.-> Cloud
+    SmartRoute -.conforms.-> IAIso
+    SmartRoute -.shares IAIso with.-> Cloud
+    SmartFeed -.conforms.-> IAIso
+    SmartFeed -.shares IAIso with.-> Cloud
+    IAIso -.governs.-> Cloud
+    classDef tool fill:#1c232d,stroke:#f5b83d,color:#efe9f5;
+    classDef std fill:#04121f,stroke:#46d6c8,color:#46d6c8;
+    classDef cloud fill:#1a1327,stroke:#a78bfa,color:#a78bfa;
+    style SmartPangolin stroke-width:3px,stroke:#ff6b6b;
+```
+
+- **SmartPangolin emits clean artifacts to SmartSeal** →
+
+Open [`site/playground.html`](site/playground.html) for the interactive version.
+
+## Part of the Smart* family
+
+One system, not nine projects — same mascot, same manifesto voice, same rule-ID style,
+all aligned to the [IAIso standard](https://github.com/SmartTasksOrg/IAIso). Each is an independent, open-source, single-purpose tool you can integrate into your own architecture:
+
+| Tool | IAIso | What it does |
+|---|---|---|
+| [SmartPrompt](https://github.com/SmartTasksOrg/sf-smartprompt) | §4 · Context | Lint before you send. Bad prompt in, bad work out — and it's your name on it. |
+| [SmartCheck](https://github.com/SmartTasksOrg/sf-smartcheck) | §2 · Verification | Check before you sign off. Catch the AI when it's confidently wrong. |
+| [SmartSeal](https://github.com/SmartTasksOrg/sf-smartseal) | §3 · Provenance | Seal what you ship. A signed receipt so anyone can verify what they received. |
+| [SmartStandard](https://github.com/SmartTasksOrg/sf-smartstandard) | §7 · Standards | Standardize before you scale. One shared, auditable convention for AI-assisted work. |
+| [SmartSim](https://github.com/SmartTasksOrg/sf-smartsim) | §8 · Foresight | Simulate before it hits you. See your role's task-by-task collapse sequence. |
+| [SmartMoat](https://github.com/SmartTasksOrg/sf-smartmoat) | §6 · Workforce | Know your moat. Score the tasks AI can't easily take — and widen them. |
+| [SmartRoute](https://github.com/SmartTasksOrg/sf-smartroute) | §5 · Orchestration | Route only what you trust. Gate agents and tools with trust scores and guardrails. |
+| [SmartFeed](https://github.com/SmartTasksOrg/sf-smartfeed) | §9 · Awareness | Distill the firehose. A tight brief of only what moves your work. |
+
+**Backed by the standard:** SmartPangolin implements **IAIso §1 · Secure Sharing**.
+**Open-source edition:** this repo is the simplified, single-purpose version, built for any org to integrate into its own architecture. SmartTasks' desktop app and [SmartTasks.cloud](https://smarttasks.cloud) run a more advanced, deeply-integrated implementation of the same IAIso governance — a separate product, not this code bundled.
+
+## Who's behind this
+
+- **Roen Branham** — CEO & AI Strategy Architect · CISSP-certified AI, security & governance architect; author of IAIso and sole inventor of the Z4 Semantic Fabric patent application. [LinkedIn](https://www.linkedin.com/in/roen-branham-167ab29/)
+- **Le Vu Tanh** — CTO & Core Engineering Lead · Chief architect of the Cortex engine; large-scale system reliability and low-latency infrastructure — the engineer who ships what gets architected. [LinkedIn](https://www.linkedin.com/in/lee-thanh-76aa8ba0/)
+
+The team behind IAIso & SmartTasks: a CISSP-certified security & governance architect
+and a large-scale systems engineer — 20+ years shipping secure, AI-driven platforms for
+regulated, blue-chip environments (Allianz, BMW, Rolls-Royce, Heidenhain).
+
+<!-- SMARTTASKS-MODELS:START -->
+## Runs on governed local models
+
+Every build ships **SHA256SUMS** and a supply-chain + red-team scan — the same provenance discipline SmartPangolin enforces on your repos.
+
+This tool is local-first, so pair it with models you can actually vet. **SmartTasks** publishes 21+ governance-validated GGUF builds on Hugging Face — each with a machine-readable **scorecard** (capability tiers L1 Layman → L5 Agentic, IAIso conformance invariants (pass/warn/fail), OWASP-mapped garak red-team, transparency probes (viewpoint-alignment / over-refusal), and per-file SHA-256). Gate model selection on evidence, not vibes — and every finding, including warnings, is published in full.
+
+→ **[SmartTasks on Hugging Face](https://huggingface.co/smarttasks)** · [Qwen3.6-27B](https://huggingface.co/smarttasks/Qwen3.6-27B-GGUF) (L5 agentic) · [react-agent-coder-llama-3.1-8b](https://huggingface.co/smarttasks/react-agent-coder-llama-3.1-8b-GGUF) (agentic coder) · [gpt-oss-20b](https://huggingface.co/smarttasks/gpt-oss-20b-GGUF) (open reasoning)
+<!-- SMARTTASKS-MODELS:END -->
+
+## Get in touch
+
+- **Companies & enterprises:** [enterprise@smarttasks.cloud](mailto:enterprise@smarttasks.cloud) — we help
+  teams integrate SmartPangolin + IAIso into their architecture so governance and
+  audit-readiness become a byproduct of how they already work.
+- **The standard:** [IAIso](https://github.com/SmartTasksOrg/IAIso) · [iaiso.org](https://iaiso.org)
+- **The product:** [SmartTasks.cloud](https://smarttasks.cloud)
+
+Built by **SmartTasks Lab**. Apache-2.0. Contributions welcome.
+
+<!-- SMARTBENCH-METRICS:START -->
+## Measured effectiveness (benchmarked)
+
+SmartTasks tests this tool against live local models, not just unit fixtures. Headline recall across difficulty levels: **100%**.
+
+**How to read this.** These come from the Smart\* *effectiveness benchmark*: a local model is driven to produce content of increasing difficulty; the tool (detects secrets (API keys, private keys, dangerous files), including base64/hex-encoded ones) is then run and its verdict scored against an independent oracle (broader than the tool's own rules, so a miss is a real gap).
+
+- **Recall** — of cases that genuinely contained the target, the share the tool caught. Low recall = coverage gap.
+- **Precision** — of what the tool flagged, the share that were real problems. Below 100% = false positives.
+- **Levels** — 0 canary · 1 basic · 2 realistic · 3 obfuscated · 4 adversarial (hardest).
+- **Invalid** — the model failed to produce the scenario (e.g. emitted a placeholder, not a real secret); not scored, so the tool is neither credited nor penalized.
+- **Sample size** — model output varies run-to-run; small *n* is noisy. Pooled numbers combine recent runs.
+
+| level | n | accuracy | precision | recall |
+|---|---|---|---|---|
+| 0 · canary | 2 | 100% | 100% | 100% |
+| 1 · basic | 8 | 100% | 100% | 100% |
+| 2 · realistic | 8 | 100% | 100% | 100% |
+| 3 · obfuscated | 7 | 100% | 100% | 100% |
+| 4 · adversarial | 8 | 100% | 100% | 100% |
+
+**What this run shows:**
+- Instrument check (canary) passes — the fixed sanity cases are all correct, so the higher-level numbers are trustworthy.
+- **Strong** at: basic, realistic, obfuscated, adversarial — near-complete recall.
+- No false positives observed (precision 100%) — the tool does not flag clean input.
+
+_Source: run `20260804T134233-fad704` · 2026-08-04T13:45:23 · model(s): llama-3.1-8b-lexi-uncensored-v2 · repeats 8. Numbers reflect these model(s); output varies run-to-run, so re-run and regenerate to refresh._
+<!-- SMARTBENCH-METRICS:END -->