ba0a49823b
Initial commit. Six modules extracted from
cubical-transport-hott-lean4/CubicalTransport/Algebra/ and
re-namespaced as `Infoductor`:
- Foundation/Meta.lean — MetaCType, MetaClassifier,
MetaArtifact, MetaPosition
(with manual mutual decEq for
MetaClassifier's recursive
lattice arms)
- Foundation/Edit.lean — Edit monad + Context comonad +
distributive law +
MetaClassifier.atPosition
with lattice laws as theorems
- Foundation/Restructure.lean — universal `restructure` (5-field
comp-shaped operation), 6 frozen
aliases, headless apply +
brokenRefs / selfConsistent /
Edit.guarded
- Foundation/MacroAlias.lean — @[macroAlias] attribute +
EnvExtension registry
- Foundation/MetaPath.lean — @[metaPath src target]
attribute + registry +
findPathsFromSource/ToTarget
- Foundation/Methodology.lean — @[methodology classifier]
attribute + registry +
deriveByTransport (walks
metaPath registry) +
tryEntryAsClosed primitive +
cubical_search reference
demonstrator
Builds clean on lean4 v4.30.0-rc2, ten oleans. No deps beyond
Lean stdlib. Sub-libs Tactics / Pantograph / Runner are planned
under the same lakefile.toml but not yet implemented.
Pairs with Pantograph as the conductor sits atop the pantograph
on an electric train. "Info-ductor" — conducts information
(structure / classifications / methodology) through a Lean
codebase.
Forgejo: http://maxgit.wg:3000/max/infoductor
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
38 lines
1.9 KiB
Text
38 lines
1.9 KiB
Text
NOTICE — Development methodology and authorship
|
|
|
|
This Software was developed under direct human creative direction with
|
|
the assistance of AI tooling (Claude, by Anthropic). AI assistance
|
|
was used analogously to an IDE, compiler, or code-completion engine:
|
|
a tool operating under continuous human supervision and review.
|
|
|
|
The Software's design, architecture, system specifications, naming,
|
|
module organisation, interface contracts, integration strategy, and
|
|
verification plan are the work of the copyright holder. AI-generated
|
|
fragments were directed, selected, audited, refined, and integrated
|
|
by the human author, who exercised final judgment on every substantive
|
|
design and correctness decision.
|
|
|
|
Per Anthropic's published Terms of Service, output ownership is
|
|
assigned to the user; the AI provider claims no rights in the
|
|
resulting code. Per United States Copyright Office guidance (August
|
|
2023, "Copyright Registration Guidance: Works Containing Material
|
|
Generated by Artificial Intelligence"), purely machine-generated
|
|
output is not eligible for copyright, while the selection,
|
|
arrangement, and creative human direction supplied by a human author
|
|
are. Those human-authored contributions — architectural decisions,
|
|
problem framing, design rationale, integration, and verification —
|
|
are the load-bearing creative contributions to this Software, and the
|
|
accompanying LICENSE asserts proprietary rights on the resulting
|
|
human-directed creative whole.
|
|
|
|
"Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>"
|
|
footers in commit messages document the development methodology in
|
|
the customary tooling-honesty convention. They are not a claim of
|
|
legal authorship by the AI and effect no transfer of rights to any
|
|
third party.
|
|
|
|
Trade-secret protection, contract law, and access controls applying
|
|
to this repository remain in force independent of the copyright
|
|
analysis above.
|
|
|
|
For licensing inquiries, contact: mgorog@gmail.com
|