v1.0.3 — Canonical author name + ORCID + Lattes

v1.0.3 — Canonical author name + ORCID + Lattes

Identity-metadata patch. Fixes the author registration across every
surface that feeds Zenodo and every surface where readers see the
author's name. Closes the "author cluster isolation" issue observed on
Zenodo for v1.0.0 through v1.0.2.

Publisher: Codex Hash Research Laboratory · São Paulo, Brazil
Author: Carlos Ulisses Flores · CTO & Chief Researcher · MSc AI candidate
ORCID: 0000-0002-6034-7765
Lattes (CNPq): 6905246706890561
Concept DOI (always latest): 10.5281/zenodo.20276631
Versioned DOI (this release): auto-minted by Zenodo within ~10 minutes

---

The problem this patch fixes

The maintainer's five other Zenodo deposits (Yape Architecture
Simulation; Cyber-Financial Resilience via Little's Law and Bayesian
LSTM; Cellular Inference Mesh; LLM Contextizer; TechGrowth DES) all
register the author as "Flores, Carlos Ulisses" with ORCID
0000-0002-6034-7765 attached. That is his canonical academic
citation form.

The first three ASP deposits (v1.0.0, v1.0.1, v1.0.2) registered the
author as "Flores, Ulisses" without an ORCID identifier. Two
consequences:

1. Zenodo could not link this deposit to the maintainer's author
   cluster → ASP appeared isolated from his other publications.
2. Citations indexers (Google Scholar, OpenAlex, Crossref) had no
   ORCID to disambiguate → the author's bibliography didn't include
   ASP.

This patch fixes the identity metadata at every layer:

Surface	Change
CITATION.cff author block	given-names: Carlos Ulisses + orcid: field added + Lattes URL as comment
CITATION.cff preferred-citation	Canonical name + ORCID
AUTHORS	Maintainer block updated with ORCID + Lattes URLs
paper/asp-preprint.md (Author block + About the Author + footer)	Canonical name + ORCID + Lattes inline
paper/iron-law-11.md	Same
Both PDFs (rebuilt)	Canonical name + ORCID + Lattes embedded in title block
README.md, index.md, 4 translations	Maintainer references updated
Publications/.../ (12 occurrences)	Signatures + frontmatter author tags aligned

---

What the maintainer must do manually in Zenodo UI

CITATION.cff fixes propagate only to new deposits. The three
existing Zenodo deposits (v1.0.0, v1.0.1, v1.0.2) already have
published metadata with the old name and still appear isolated. To
retroactively link them to the maintainer's author cluster:

For each deposit (v1.0.0 → 20276632, v1.0.1 → 20276855, v1.0.2 → 20276900):

1. Open the deposit on Zenodo
2. Click Edit
3. In Creators:
   • Change "Flores, Ulisses" → "Flores, Carlos Ulisses"
   • Add ORCID 0000-0002-6034-7765
   • (Optional) Add the Lattes URL as an additional identifier
4. Save (no new version mint required for metadata-only edits)

After that, all four deposits (v1.0.0 through v1.0.3) link to the
maintainer's author cluster and appear in his bibliography.

---

What is unchanged

• The empirical claim (60.0% silent-refusal rate; 95% CI 46.5%–73.6%; N=50
  pre-registered) is identical.
• The methodology, the protocol, the source code, and every evidence
  file are unchanged.
• The concept DOI (10.5281/zenodo.20276631) continues to resolve to
  the latest version — which after publication is v1.0.3.

This is purely an identity-metadata patch. No retraction, no correction
to substance, no addendum to claims.

---

Cite this work (preferred)

Flores, C. U. (2026). ASP — Anticipating Shadow Points.
Codex Hash Research Laboratory Whitepaper Series.
https://doi.org/10.5281/zenodo.20276631

(Concept DOI; auto-resolves to the latest version. The canonical name
"Flores, Carlos Ulisses" is now consistent across CITATION.cff,
Zenodo deposit metadata for v1.0.3+, and the maintainer's other
publications.)

---

Verification (all green pre-commit)

• CITATION.cff parses as valid YAML
• tests/iron-law-11/scripts/verify-prereg.sh → OK (50 scenarios hashed)
• benchmark/.venv/bin/pytest -q → 27/27 passed
• PDFs rebuilt cleanly from .md source with new author block
• Zero standalone "Ulisses Flores" occurrences in Publications/
  (12 canonical "Carlos Ulisses Flores" references)

---

Mantra (still holds)

Not a bit of unnecessary file at the Zenodo-minted tag.
Citations age gracefully via the concept DOI.
The author appears under his canonical name across all surfaces.

v1.0.2 — Concept DOI is primary citation anchor

v1.0.2 — Concept DOI is now the primary citation anchor

Patch release — Zenodo automatically maintains a concept DOI alongside
each versioned DOI. v1.0.2 makes the concept DOI the primary citation
anchor across CITATION.cff, both whitepapers' status blocks, the rebuilt
PDFs, and the top-level README.

Publisher: Codex Hash Research Laboratory · São Paulo, Brazil
Author: Ulisses Flores · CTO & Chief Researcher
Concept DOI (always latest): 10.5281/zenodo.20276631
Versioned DOI (this release): auto-minted by Zenodo within ~10 minutes

---

The DOI map for this work

What	DOI	When to use
Concept (always latest)	10.5281/zenodo.20276631	Default for citations — ages gracefully
v1.0.0 (specific snapshot)	10.5281/zenodo.20276632	Pin a reviewer audit to v1.0.0's exact bytes
v1.0.1 (specific snapshot)	10.5281/zenodo.20276855	Pin to v1.0.1 (PDFs with embedded DOI)
v1.0.2 (specific snapshot)	minted automatically on this release publish	Pin to v1.0.2 (concept DOI integrated everywhere)

All four DOIs resolve. Concept DOI is preferred for citations because
a citation written today to 20276631 still resolves to the most recent
version in 2027, 2030, 2040 — no citation drift.

---

What changed since v1.0.1

CITATION.cff

• identifiers[] now lists the concept DOI first.
• Each versioned DOI (v1.0.0, v1.0.1) is kept as an additional entry
  for use cases that need to pin a specific snapshot (reproducibility,
  reviewer audits).
• preferred-citation.doi is the concept DOI.

paper/asp-preprint.md and paper/iron-law-11.md

• Status block now shows the concept DOI with
  (concept · always resolves to latest version) note.
• Both PDFs rebuilt so the concept DOI appears in their rendered title
  block.

Top-level README.md

"Whitepapers" section linked to the concept DOI instead of the v1.0.0
versioned DOI.

---

What stays the same

The empirical claim (60.0% silent-refusal rate; 95% CI 46.5%–73.6%; N=50
pre-registered), the methodology, the protocol, the source code, and
all evidence files are unchanged. This is a citation-hygiene patch.

For the headline finding, methodology, citation block, reproducibility
instructions, license terms, and acknowledgments, see the v1.0.0
release notes.

---

Cite this work (preferred)

Flores, U. (2026). ASP — Anticipating Shadow Points.
Codex Hash Research Laboratory Whitepaper Series.
https://doi.org/10.5281/zenodo.20276631

---

Mantra (still holds)

Not a bit of unnecessary file at the Zenodo-minted tag.
Citations age gracefully via the concept DOI.

v1.0.1 — Zenodo DOI embedded; paper/ cleanup completed

v1.0.1 — Zenodo DOI embedded; paper/ cleanup completed

Patch release following v1.0.0. Embeds the Zenodo-minted DOI throughout
citable surfaces and finishes the paper/ directory cleanup that should
have shipped in v1.0.0.

Publisher: Codex Hash Research Laboratory · São Paulo, Brazil
Author: Ulisses Flores · CTO & Chief Researcher
DOI (versioned): this release · auto-minted by Zenodo within ~10 minutes of publication
DOI (concept, auto-points to latest): 10.5281/zenodo.20276631
DOI (v1.0.0, original): 10.5281/zenodo.20276632

The empirical claim, the methodology, the protocol, the pre-registration,
and the source code did not change between v1.0.0 and v1.0.1. This is a
publishing-hygiene patch.

---

What changed since v1.0.0

1. DOI embedded in every citable surface

• CITATION.cff — new identifiers entry of type doi;
  preferred-citation carries the DOI directly. GitHub's "Cite this
  repository" button presents it.
• paper/asp-preprint.md — Status block includes a DOI line.
• paper/iron-law-11.md — same.
• Both PDFs rebuilt so the DOI appears in the published artefact
  too.

2. paper/ directory cleanup

At v1.0.0 the paper/ directory contained the .md sources, a
Makefile, a header.tex, and a .gitignore — but NOT the PDFs
themselves. The PDFs were gitignored as "derived artefacts" while a
build system that produces them sat in their place. Under the
maintainer's repo principle (artefato de geração ≠ produto gerado),
the inversion is wrong: the PDFs are the papers; the build system is
the generation.

Resolved at v1.0.1:

Action	Files
Added	paper/asp-preprint.pdf, paper/iron-law-11.pdf
Removed	paper/Makefile, paper/header.tex, paper/.gitignore, paper/README.md

The pandoc + tectonic build recipe + the Unicode-→-math-mode header
content are preserved verbatim as a code-fence inside
CONTRIBUTING.md § Rebuilding the whitepaper PDFs.

Final paper/ at this tag (4 files):

paper/
├── asp-preprint.pdf    ← Whitepaper 1
├── asp-preprint.md     ← canonical source
├── iron-law-11.pdf     ← Whitepaper 2
└── iron-law-11.md      ← canonical source

3. Redundant .gitkeep placeholders removed

• benchmark/runs/.gitkeep
• tests/iron-law-11/runs/.gitkeep
• tests/iron-law-11/smoke/runs/.gitkeep

In each case the parent directory either had real tracked content
underneath (runs/published/<id>/) making the .gitkeep trick
redundant, or the directory was intentionally gitignored and didn't
need an in-tree placeholder.

4. Top-level README.md "Whitepapers" section

New section linking directly to the in-repo PDFs and to the Zenodo DOI
for the citable version; companion link to the rebuild instructions in
CONTRIBUTING.md.

---

Same as v1.0.0

The substance does not change: 60.0% silent-refusal rate on the
pre-registered N=50 protocol, 95% Clopper-Pearson CI 46.5%–73.6%. The
falsification verdict still triggers the "mandatory safe-parsing recipe

• Anthropic notification" outcome per pre-registered §3.6.

For the headline finding, methodology, citation block, reproducibility
instructions, license terms, and acknowledgments, see the v1.0.0
release notes.

---

Attached assets

Same three assets as v1.0.0, but the PDFs now have the DOI embedded in
their rendered title block.

• asp-preprint.pdf
• iron-law-11.pdf
• iron-law-11-trial-dataset-v1.0.0.zip (unchanged — the protocol's
  N=50 dataset is locked at the v1.0.0 tag by pre-registration)

---

Cite this work

Either DOI resolves to the work:

• Versioned (this release): this Zenodo deposit (minted ~10 min after Release publication)
• Concept (always latest): 10.5281/zenodo.20276631

Recommended citation:

Flores, U. (2026). ASP — Anticipating Shadow Points.
Codex Hash Research Laboratory Whitepaper Series.
https://doi.org/10.5281/zenodo.20276631

(Concept DOI tracks the most recent version automatically.)

---

Verification (all green pre-commit)

• tests/iron-law-11/scripts/verify-prereg.sh → OK (50 scenarios hashed)
• benchmark/.venv/bin/pytest -q → 27/27 passed
• python3 -c "import yaml; yaml.safe_load(open('CITATION.cff'))" → valid
• paper/ contains exactly 4 files (2 PDFs + 2 .md)
• Zero "fill in" / <placeholder> strings in any in-tree file

---

Mantra (still holds)

Not a bit of unnecessary file at the Zenodo-minted tag.

v1.0.0 — Codex Hash Research Laboratory Whitepaper Series · 2026

v1.0.0 — Codex Hash Research Laboratory Whitepaper Series · 2026

First stable public release. Two independent technical whitepapers, a
pre-registered N=50 protocol with frozen per-trial dataset, a Claude
Code skill, and a deterministic adjudicator with cryptographic
provenance — all under a single release.

Publisher: Codex Hash Research Laboratory · São Paulo, Brazil
Author: Ulisses Flores · CTO & Chief Researcher
DOI: 10.5281/zenodo.20276632

Note on patches: a v1.0.1 follow-up to this release (a) embeds the
DOI inline in CITATION.cff and both papers' status blocks, (b) ships
the rebuilt PDFs as in-repo artefacts at paper/asp-preprint.pdf and
paper/iron-law-11.pdf, and (c) removes generation-only files
(Makefile, header.tex, redundant .gitkeeps) per the maintainer's
repo principle that artefato de geração ≠ produto gerado. The same
DOI's concept identifier auto-points to whichever is the most recent
version.

---

Headline empirical finding

On a pre-registered N=50 protocol against Claude Code 2.1.143 (Claude
Opus 4.7), claude -p returns exit code 0 on 30 of 50 graceful agent
refusals (60.0%; 95% Clopper–Pearson CI 46.5%–73.6%).

Safety-refusal scenarios produced 100% silent refusal of model-level
responses. Overall misclassification rate of "exit_zero ⇒ semantic
success": 88.0% (95% CI 75.7%–95.5%).

A shell wrapper of the form claude -p "$GOAL" && next_step will
silently mis-route the majority of agent refusals as task successes.
The six-line safe-parsing recipe in Whitepaper 2 §4 is mandatory for any
production pipeline wrapping the CLI.

The protocol's analysis plan, the 50 scenario prompts, the locked
refusal-phrase list, the random seed, and the falsification thresholds
were committed to git at commit 5c656f1 before any data collection
— eliminating HARKing and p-hacking concerns standard in clinical-trial-
style empirical ML.

---

What's in this release

Whitepapers (attached as binary assets)

• asp-preprint.pdf — ASP: An Operational Pre-Mortem Skill for LLM
  Coding Agents — An Experience Report (~5,300 words). Documents the
  13-phase Claude Code skill with 12 Iron Laws, integrating Mitchell-Russo-
  Pennington (1989) prospective hindsight, Klein (2007), Cemri et al.
  (2025) MAST 14-mode failure taxonomy, Erdogan et al. (2025) planner-
  executor separation, and the limits of intrinsic LLM self-correction
  (Huang et al. 2024; Tyen et al. 2024; Zheng et al. 2023).

• iron-law-11.pdf — Graceful Refusals as Silent Successes: A
  Pre-Registered Protocol for Characterising claude -p Exit-Code
  Semantics (~5,500 words including the empirical addendum). Pre-
  registered methodology + N=50 confusion matrix + Clopper-Pearson 95% CI

  • three constructive options for the Anthropic Claude Code team.

Per-trial dataset (attached as binary asset)

• iron-law-11-trial-dataset-v1.0.0.zip — frozen per-trial dataset
  for the N=50 run (267 KB, 355 files). Each trial directory contains
  the verbatim prompt sent to claude -p, the captured exit code, the
  full JSON envelope returned, the extracted text response, and
  wall-clock timing. All artefacts SHA-256-hashed in the
  preregistration.json committed at the pre-registration commit
  5c656f1.

Companion source code

• ASP skill — skills/anticipating-shadow-points/ — 13-phase
  pre-mortem-first planning protocol distributed as a Claude Code
  plugin. Three install paths (plugin marketplace, dev mode, standalone
  script).
• Pre-registered protocol scripts — tests/iron-law-11/ — runnable
  scaffolding to reproduce the N=50 protocol on any Claude Code
  installation in ~10 minutes for ~$5 inference.
• Python benchmark — benchmark/ — deterministic 4-layer
  adjudicator (exact / synonym / Jaccard / unmatched) with SHA-256
  Merkle-style hash chain over env + code + inputs + outputs +
  adjudication. 27/27 unit tests.

---

Cite this work

Flores, U. (2026). ASP — Anticipating Shadow Points (v1.0.0).
Codex Hash Research Laboratory Whitepaper Series.
https://doi.org/10.5281/zenodo.20276632

(See CITATION.cff for machine-readable format; GitHub's "Cite this
repository" button uses it automatically.)

The four primary methodological sources cited across both whitepapers
should be cited alongside ASP when discussing the methodology:

• Mitchell, D. J., Russo, J. E., & Pennington, N. (1989). Back to the
  Future. J. Behavioral Decision Making 2(1), 25–38.
• Klein, G. (2007). Performing a Project Premortem. HBR 85(9).
• Cemri, M., et al. (2025). Why Do Multi-Agent LLM Systems Fail?
  arXiv:2503.13657 (κ=0.88 on 1,600+ annotated traces).
• Huang, J., et al. (2024). Large Language Models Cannot Self-Correct
  Reasoning Yet. ICLR 2024 (arXiv:2310.01798).

The full bibliography (26 verified primary entries + 3 documentation
references) is in each whitepaper's References section.

---

License

• Software (ASP skill, benchmark, protocol scripts, plugin
  manifests, all repository code): MIT.
• Whitepaper text (PDFs and .md sources under paper/):
  CC BY 4.0.

When reusing methodology figures or significant passages, please cite
the work as above.

---

Reproducibility

The pre-registered protocol is reproducible end-to-end in ~10 minutes
for ~$5 inference. Anyone with claude on $PATH and a Claude Code
plan can verify (or refute) the headline finding:

git clone https://github.com/ulissesflores/anticipating-shadow-points
cd anticipating-shadow-points/tests/iron-law-11

# 1. Verify the pre-registration hash chain is intact
./scripts/verify-prereg.sh

# 2. Re-run the formal N=50 protocol against your installation
./scripts/run-protocol.sh

# 3. Analyse with the pre-committed analysis script
./scripts/analyze.py runs/<your-run-id>

To rebuild the whitepaper PDFs from the canonical .md sources, see
CONTRIBUTING.md § Rebuilding the whitepaper PDFs.

The benchmark package's deterministic adjudicator is reproducible
across machines (manifest hashes match):

cd benchmark
python -m venv .venv && .venv/bin/pip install -e ".[dev]"
.venv/bin/pytest                 # 27 passed

---

Pre-registration integrity

The Iron Law 11 protocol was pre-registered in git at commit 5c656f1
on 2026-05-18 before any data was collected. SHA-256 hashes of all 50
scenarios + the refusal-phrase list + the random seed are recorded in
tests/iron-law-11/preregistration.json. The verification script
tests/iron-law-11/scripts/verify-prereg.sh returned OK immediately
before formal dispatch and immediately after analysis. No deviations
from the pre-registration occurred.

The falsification thresholds (Whitepaper 2 §3.6) were committed before
data collection. The observed silent-refusal rate of 60.0% exceeds the
25% threshold, triggering the pre-registered recommendation: safe-
parsing recipe is mandatory; Anthropic notification recommended.

---

What is intentionally NOT in this repo

Per the maintainer's principle artefato de geração ≠ produto gerado,
the following live outside the repo:

• Launch operations (social-media post drafts, posting calendar,
  engagement playbook, status tracker) live at ~/Developer/Publications/ anticipating-shadow-points/v1.0.0-launch/, designed for a separate
  agent (or the human author manually) to execute the rollout.
• Build journals (advisor logs, demo template instantiations,
  intermediate closure reports, smoke-test outputs) live in git history
  but are not in-tree at this release.

Every byte in this release has a justification as a citable product.

---

Companion external resources

• Documentation site: https://ulissesflores.github.io/anticipating-shadow-points/
• Maintainer: https://ulissesflores.com
• Contact: c.ulisses@gmail.com
• MSc affiliation: American Global Tech University (in progress)

---

Acknowledgments

This research was prepared in explicit human-in-the-loop collaboration
with Claude (Anthropic, Opus 4.7), used as a drafting and verification
partner. Methodology decisions, empirical design, and finalisation were
performed by the human author. The work is published under his name
alone; see AUTHORS and docs/ARCHITECTURE.md Parts 5–6 for the
collaboration model.

The author thanks the maintainers of obra/superpowers, the contributors
of agentskills.io, and the Anthropic Claude Code team for the /goal
primitive and the --output-format json flag — the latter is exactly
the right primitive; this protocol exists because it exists.

v0.3.0 — Research-release artifacts (preprint + announcement templates + privacy)

v0.3.0 — Scientific-style research release

This release transitions ASP from an open-source plugin release to a research release, adding the foundation artifacts academic CS expects and channel-specific announcement templates.

What's new

Research foundation:

• LaTeX preprint source ready for arXiv submission under paper/ (10 pages, ~3000 words: abstract, intro, related work, the ASP protocol, empirical evaluation, the claude -p /goal finding, discussion, limitations, future work, references, two appendices).
• BibTeX bibliography with all foundational citations.
• arXiv submission checklist in paper/README.md.
• PRIVACY.md notice — explicit, honest, client-side-only statement.
• CITATION.cff updated with placeholders for arXiv ID and Zenodo DOI.

Staged announcement templates under social/:

• LinkedIn long-form article (~2000 words).
• Twitter/X 12-tweet thread + canned responses.
• Hacker News Show HN submission + 7 anticipated-critique answers.
• r/MachineLearning [R]-tagged post with methodology defenses.
• Hugging Face Papers submission instructions.
• Bluesky / Mastodon fediverse adaptation.
• Personal blog post outline for ulissesflores.com.
• social/README.md with staging plan, anti-patterns, and cross-channel consistency rules.

What's NOT in this release

Plugin / skill / methodology content is unchanged. v0.3.0 is purely additive scientific-release infrastructure. Existing claude plugin install users do not need to upgrade unless they want the new docs.

Next steps (user-driven, off-repo)

1. Submit paper/asp-preprint.tex to arXiv (cs.AI primary, cs.SE cross-list).
2. Activate Zenodo DOI via the GitHub-Zenodo integration (one-time OAuth + tag a release).
3. Stage social posts per social/README.md cadence (LinkedIn week 2, Bluesky/Mastodon week 2, r/ML week 2, Twitter/HN week 3, HF Papers post-arXiv).
4. Optional: long-form blog post at ulissesflores.com (week 3-4).

v0.2.3 — Version alignment + marketing-first landing/README

v0.2.3 — Version alignment release

This release tags the marketing-first redesign of the landing page (index.md) and README.md that shipped between v0.2.2 and this tag, plus bumps the visible version fields in plugin.json and CITATION.cff so they match the release tag.

What's in this release

• index.md (Pages homepage) — completely rewritten as a SOTA OSS marketing landing following patterns from shadcn/ui, biomejs.dev, bun.sh, htmx.org, and claude.com/product/claude-code. Hero is action/benefit oriented; proof block appears immediately after hero; feature grid as visual cards; demo block; clear install CTA. Citation/academic links demoted to dense small-text footer.
• README.md — same marketing-first structure adapted for the GitHub repo home audience: kept badges, language switcher inline, three install paths with collapsible details for B/C, dedicated Troubleshooting section.
• plugin.json version 0.2.0 -> 0.2.3 so claude plugin details shows the right number.
• CITATION.cff version 0.2.1 -> 0.2.3 so the academic citation matches.

What did NOT change

Skill behavior, methodology, Iron Laws, templates, evals, scripts, plugin format, marketplace integration. This is purely a docs + metadata release.

Upgrade for existing installs

claude plugin marketplace update anticipating-shadow-points
claude plugin uninstall anticipating-shadow-points
claude plugin install anticipating-shadow-points@anticipating-shadow-points

v0.2.2 — SOTA community files + author profile

Docs/meta patch adding all standard OSS community files (CITATION.cff, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, AUTHORS, AGENTS, CHANGELOG, issue/PR templates, FUNDING placeholder) and populating the author profile across manifests and READMEs. No code or behavior change. See CHANGELOG.md for the full list.

v0.2.1 — Use Cases sections (5 langs) + GitHub Pages homepage

v0.2.1 — Form-submission ready

Patch release polishing for the Anthropic plugin directory submission form.

What's new

• Explicit "Example Use Cases" section added to README.md (English) and equivalents in 4 translations (ES/PT/IT/HE). 6 concrete user-facing scenarios derived from the 5 evals.
• Plugin homepage now points to a dedicated GitHub Pages site: https://ulissesflores.github.io/anticipating-shadow-points/ (just-the-docs theme, search-enabled, multilingual nav).
• Troubleshooting section added covering the SSH→HTTPS workaround, recall.py opt-in, plugin name doubling explanation, and /asp vs /anticipating-shadow-points:asp invocation differences.
• CI fixes: paths updated post-v0.2.0 restructure (skills/anticipating-shadow-points/, commands/); plugin.json + marketplace.json validation added; verify.sh unused-var cleanup.

Why this matters

The Anthropic plugin submission form (claude.ai/settings/plugins/submit) asks for:

• Link to plugin → repo URL ✓
• Plugin homepage → now ulissesflores.github.io/anticipating-shadow-points/ ✓
• Example use cases → dedicated section in README ✓

No behavior changes

All 12 Iron Laws preserved. scripts/verify.sh still 20/20 PASS. Plugin manifest still valid.

v0.2.0 — Native plugin format + self-host marketplace + triple-distribution

v0.2.0 — Plugin format conversion

Major restructure following Anthropic's published plugin spec (code.claude.com/docs/en/plugins). ASP now ships in three install paths simultaneously with full plugin marketplace support.

What changed

New plugin manifest layer:

• `.claude-plugin/plugin.json` — official manifest (name, version, author, repository, license, keywords)
• `.claude-plugin/marketplace.json` — repo is now its own marketplace (one-step `/plugin marketplace add` install)

Directory restructure (spec-compliant):

• `skill/` → `skills/anticipating-shadow-points/` (plural + per-skill subdirectory)
• `command/` → `commands/`
• `install.sh` and `verify.sh` source paths updated accordingly
• All skill content, templates, evals preserved verbatim (git mv with rename detection)

Three install paths

Path A — Plugin marketplace (recommended)

```
/plugin marketplace add ulissesflores/anticipating-shadow-points
/plugin install anticipating-shadow-points@anticipating-shadow-points
```
Invocation: `/anticipating-shadow-points:asp `. Native update via `/plugin update`.

Path B — Dev mode

```
claude --plugin-dir ~/Developer/ASP
```
Same namespaced invocation. Session-only.

Path C — Standalone script (legacy)

```
./scripts/install.sh
```
Bare invocation `/asp`. Verify with `./scripts/verify.sh` (20/20 PASS).

Empirical validation (2026-05-17)

Plugin smoke test via `claude -p --plugin-dir` confirmed all four invocation aliases (`asp`, `anticipating-shadow-points`, `anticipating-shadow-points:asp`, `anticipating-shadow-points:anticipating-shadow-points`) appear in session `slash_commands` + `skills` lists. Cost: $0.13.

No behavior changes

All 12 Iron Laws preserved. All phases unchanged. All Iron Law 11 discipline (parse JSON, never trust $?) intact. v0.1.x users on Path C: re-run `./scripts/install.sh --force` to pick up new source layout.

Docs updated

• `README.md`: three install paths with examples
• `docs/ARCHITECTURE.md`: Section 8.7 (triple-distribution as novel SOTA contribution)
• All 5 multilang READMEs link to ARCHITECTURE.md

v0.1.1 — Comprehensive ARCHITECTURE.md (state-of-the-art design doc)

v0.1.1 — Documentation patch

Adds docs/ARCHITECTURE.md, a 10-part state-of-the-art design document covering the full journey from v1 to v5:

• Academic foundations (Klein, MAST, Plan-and-Act, Reflexion, Plan-Validate-Execute, /goal)
• Community/industry state and the gap ASP fills
• v1 -> v5 architectural pivots with each pivot's trigger and discovery
• Empirical discoveries (2026-05-17 battery, including the Critical Finding C: `claude -p` returns exit 0 even on graceful refusal — Iron Law 11 derivation)
• User contributions (especially the lateral move proposing `claude -p` as subprocess to invoke `/goal`)
• Advisor reviews (3 calls, 1 pre-ship functional bug caught in Iron Law 9 enforcement)
• Derivation of all 12 Iron Laws mapped to specific papers / findings / incidents
• What is genuinely novel in ASP
• Open questions and future work
• Full references (academic + Anthropic + community + internal probe files)

Links added to all 5 READMEs (EN/ES/PT/IT/HE).

No code changes. Pure documentation patch.