Skip to content

docs(api): correct stale memory-type taxonomy in published READMEs#2447

Merged
nicoloboschi merged 1 commit into
vectorize-io:mainfrom
r266-tech:fix/readme-memory-type-taxonomy
Jun 30, 2026
Merged

docs(api): correct stale memory-type taxonomy in published READMEs#2447
nicoloboschi merged 1 commit into
vectorize-io:mainfrom
r266-tech:fix/readme-memory-type-taxonomy

Conversation

@r266-tech

Copy link
Copy Markdown
Contributor

The top "features" bullet of both primary published packages misstates the recall memory-type taxonomy:

hindsight-api/README.md:124 and hindsight-api-slim/README.md:124 (byte-identical):

Three Memory Types — World facts, bank actions, and formed opinions with confidence scores

The live taxonomy is world / experience / observation (VALID_RECALL_FACT_TYPES in hindsight-api-slim/hindsight_api/engine/response_models.py, and the fact_type IN (...) CHECK constraint):

  • opinion was removed (recall now 422-rejects it)
  • bank was renamed to experience

So the first thing a PyPI/GitHub visitor reads tells them opinion is a valid recall fact_type (it isn't) and references bank (which no longer exists). This syncs the bullet to the live enum, matching hindsight-docs/docs/developer/index.mdx.

Scoped to that one bullet — opinion formation as a behavioral concept (e.g. ReflectResult) is untouched.

The top feature bullet of both primary published packages (hindsight-api
and hindsight-api-slim) says 'World facts, bank actions, and formed
opinions', but the live recall taxonomy is world/experience/observation:
'opinion' was removed (recall now 422-rejects it) and 'bank' was renamed
to 'experience'. Sync the bullet to VALID_RECALL_FACT_TYPES so the first
thing a PyPI/GitHub visitor reads matches the actual API contract.

Scoped to the taxonomy bullet only; opinion *formation* as a behavior is
unchanged.
@nicoloboschi nicoloboschi merged commit a5b752a into vectorize-io:main Jun 30, 2026
86 of 87 checks passed
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.

2 participants