03Learning Engine

Keep the source.
Keep the judgment.

A personal learning project for organizing source-linked material and retrieving reviewed records, with human review at the boundary of authoritative memory.

What the project is for

Learning Engine addresses a practical problem: how to make learning notes retrievable without losing their sources, review state, or limitations. The project is intended for its owner’s personal use.

The legacy public integration was named Learning Engine n8n. Its documentation described a designated Google Drive folder and a locally operated n8n workflow. The owner confirmed on 13 October 2026 that this bridge has been retired. Its documentation is historical and does not describe the current project’s full deployment.

A high-level view

Conceptual responsibilities. This figure is not a verified deployment topology or an automatic source-to-memory pipeline.

Evidence available here

Observed

Public documentation

The legacy homepage, Privacy, and Terms pages were accessible over HTTPS on 13 October 2026.

Observed · bounded

Read-only memory retrieval

A retrieval call returned records with source references and explicit validity information during this website’s preparation. This demonstrates that bounded retrieval call; it does not establish full ingestion coverage or workflow completion.

Not established here

End-to-end operation

The legacy Google Drive/n8n bridge is retired. This website does not establish current ingestion coverage, automated processing, deletion behavior, or continuous availability of the separate private learning services.

What the project does not establish

  • A retrieved or generated answer is not a substitute for checking its source.
  • The presence of a paper or note does not establish mastery.
  • A candidate or derived index is not automatically an authoritative record.
  • A successful component check does not establish the success of an entire learning workflow.

Data and access

This website provides project information. It does not accept learning requests, connect visitors to the private knowledge base, or collect Google authorization tokens.

Information about the legacy integration’s processing, retention, and revocation is described in the privacy policy. The policy distinguishes project data processing from website hosting and traffic measurement.

Related material

Public information repository ↗
Privacy policy · Terms of use

General questions can be raised in the public project tracker. Do not include private notes, credentials, or account information.