Skip to content

docs: describe Isopace as a Go package, not a framework#21

Open
canaan5 wants to merge 1 commit into
mainfrom
docs/package-not-framework
Open

docs: describe Isopace as a Go package, not a framework#21
canaan5 wants to merge 1 commit into
mainfrom
docs/package-not-framework

Conversation

@canaan5

@canaan5 canaan5 commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Repositions the product wording from "framework" to "package" for consistency with how Isopace is actually distributed (a Go module/package).

What changed

  • Public docs/copy: README, docs/index.md, docs/getting-started.md, docs/examples.md, docs/packages.md, CHANGELOG.md, ARCHITECTURE.md, IMPLEMENTATION_PLAN.md.
  • Per-file license header: // This file is part of Isopace, a financial transaction framework....package. across all 173 .go files plus CONTRIBUTING.md and docs/contributing.md.

Scope / safety

  • Comment- and docs-only. No code or behavior change; go build ./... passes.
  • Legal/commercial wording left intactCOMMERCIAL-AGREEMENT.md, COMMERCIAL-LICENSE-CHECKLIST.md, and ROADMAP-to-v1.md still use "framework" where the term carries liability/scoping meaning.

183 files changed, comment/text only.

Reposition product wording across README, docs, CHANGELOG, ARCHITECTURE,
and the per-file license header (175 files) from "framework" to
"package". Comment/doc-only; no code or behavior change. Legal/commercial
agreement wording left intact.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant