Files
zeekayandHanzo Dev 1cd0cd7644 semantic: the pipeline, end to end
The first commit was the shape. This is the implementation: every stage of the
pipeline, the graph and its measures, the type system over it, entailment,
deduplication and conflict resolution, the decision layer, the stores and the
export formats. Twenty-six thousand lines of Go and sixteen thousand of tests,
against no dependency but the standard library.

Where the Python reaches for torch, spacy or a database driver, the Go states
an interface and reports what is missing rather than pretending. A caller can
tell "this build cannot serve that" from "nobody has heard of it", which is the
difference between a port and a stub. The deterministic paths are complete and
are what the tests exercise; the model-shaped ones are one adapter away.

Porting a bug is not parity, so several places now disagree with the original
on purpose. The JSON repair that closed a truncated reply counted each bracket
kind separately and closed them backwards on the one input it exists for; it
now works off a stack and ignores brackets inside strings. The entity patterns
joined words with \s, so a heading ran into the sentence beneath it and became
one name while the real relation was lost; a name is separated by horizontal
space now. Eigenvector centrality ran plain power iteration, which on a
bipartite graph swings between the two ends of a sign-paired eigenvalue forever
and reported every node in a star as equally central; it iterates with A+I,
which moves no eigenvector and settles. Similarity summed its weighted parts in
map order, and float addition is not associative, so the same comparison scored
differently between runs and duplicate detection returned a different answer
each time. An inferred ontology named object-property endpoints by raw source
type and data-property endpoints by class, so the schema referred to classes it
did not contain. A property with no IRI of its own was minted as a class and
came back Pascal-cased, renaming the term on the way out of the document.

The command built a pipeline with every stage nil and panicked on each
invocation. It is now the composition the package documents, and Run reports a
missing ingester instead of dereferencing it.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-08 12:57:59 -07:00

42 lines
1.2 KiB
Go

// Package prov records where a value came from, in W3C PROV-O terms: an
// Entity was generated by an Activity, which was run by an Agent. Keeping
// the vocabulary means the record joins other PROV data without translation.
package prov
import "time"
// Entity is a thing whose origin is being recorded: a document, a chunk, a
// triple, a graph. It names the activity that produced it and the entities it
// was derived from, so a claim can be walked back to its sources.
type Entity struct {
ID string
GeneratedBy string // Activity.ID
DerivedFrom []string
}
// Activity is something that happened over an interval and produced entities:
// an ingest, an extraction, a merge. Used lists what it read.
type Activity struct {
ID string
Kind string
Agent string // Agent.ID
Start time.Time
End time.Time
Used []string // Entity.ID
}
// Agent is whoever bears responsibility for an activity — a person, a program,
// or the organization either acts for.
type Agent struct {
ID string
Kind string // person, software, organization
}
// Log is the append-only record the three types are written to.
type Log interface {
Entity(Entity) error
Activity(Activity) error
Agent(Agent) error
Trace(id string) ([]Activity, error)
}