kami
6c92f85d10
Bring the Nexus/Praxis/Hexis integration in line with MAVEN_ECOSYSTEM_ARCHITECTURE.md: - Praxis over HTTP: drop the in-process praxis.db open (praxisstore/ praxistools) and call praxisd's /api/v1/tools/* API via a new praxisClient. Honors the "no component reads another's DB" invariant (AC#12). PraxisConfig.DBPath -> URL. - Hexis confirmation gate: mutating capabilities (ReadOnly=false) now park a bound pendingHexis confirmation and require a spoken "да" before executing; read-only run immediately (AC#7, no auto attention->action). - Capability safety: >1 verb match is ambiguous -> ask instead of firing the first; ambiguous Nexus resolution asks for clarification (AC#2). - Correlation IDs on Hexis execute, recorded in the cross-service trace. - Bug: importance arrives as JSON float64 over HTTP, not int. - Tests: confirm-gate, decline, read-only, and ambiguity paths. Build: vendor/ bakes in the hexis client (replace-directed at a sibling repo outside the Docker context); Dockerfile builds from vendor and no longer `go mod download`s the unreachable replace paths. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
26 lines
1.5 KiB
Plaintext
26 lines
1.5 KiB
Plaintext
SQLite Is Public Domain
|
|
|
|
All of the code and documentation in SQLite has been dedicated to the public
|
|
domain by the authors. All code authors, and representatives of the companies
|
|
they work for, have signed affidavits dedicating their contributions to the
|
|
public domain and originals of those signed affidavits are stored in a firesafe
|
|
at the main offices of Hwaci. Anyone is free to copy, modify, publish, use,
|
|
compile, sell, or distribute the original SQLite code, either in source code
|
|
form or as a compiled binary, for any purpose, commercial or non-commercial,
|
|
and by any means.
|
|
|
|
The previous paragraph applies to the deliverable code and documentation in
|
|
SQLite - those parts of the SQLite library that you actually bundle and ship
|
|
with a larger application. Some scripts used as part of the build process (for
|
|
example the "configure" scripts generated by autoconf) might fall under other
|
|
open-source licenses. Nothing from these build scripts ever reaches the final
|
|
deliverable SQLite library, however, and so the licenses associated with those
|
|
scripts should not be a factor in assessing your rights to copy and use the
|
|
SQLite library.
|
|
|
|
All of the deliverable code in SQLite has been written from scratch. No code
|
|
has been taken from other projects or from the open internet. Every line of
|
|
code can be traced back to its original author, and all of those authors have
|
|
public domain dedications on file. So the SQLite code base is clean and is
|
|
uncontaminated with licensed code from other projects.
|