993 · open source · provenance

Projects worth following

Two GitHub projects were installed and audited locally as possible inputs for the 993 knowledge base. This page keeps their provenance visible and their data boundaries honest: a repository can inspire an importer without becoming a source of facts by itself.

Browse the 993 manual indexOpen torque dataBack to the 993 catalogue

Projects audited
2
993 corpus imported
0
Manual procedures
235
Technical data rows
111
Torque rows
195

01

What actually feeds this site

The live 993 reference area is fed by the structured manual index already reviewed in this repository: 235 procedure entries, 111 technical-data rows and 195 torque rows. It links and summarizes source facts; it does not ship the factory manual itself.

The two GitHub repositories below are research inputs, not an automatic licence to copy their code, documents, models or community text.

External index required

Porsche 993 Assistant

Scope: Porsche 993

A Streamlit repair assistant whose vector knowledge base is queried from Pinecone and answered with Claude.

Audited commit
fa2479f511a3
Repository files
7
Licence note
not-declared

Useful here

  • The repository structure is a useful reference for a future 993 assistant.
  • The source names the forums and technical material that its external index is intended to cover.

Not imported

  • The 138,000+ knowledge chunks are not present in the Git repository.
  • No forum text, embeddings, PDFs or scraped pages were copied into porschefanatics.
  • The application needs Pinecone, Anthropic and AWS credentials that are not part of this site.

Architecture reference only

FLAT·SIX

Scope: Boxster/Cayman 981/987 and 911 991

A generation-scoped maintenance application with structured knowledge, service planning, models and an MCP assistant.

Audited commit
d00112586910
Repository files
592
Licence note
MIT for application code; bundled assets and documents are separate

Useful here

  • Generation-keyed bundles are a good guard against showing facts from the wrong Porsche generation.
  • Its source-linked knowledge shape is a useful model for a future 993 knowledge bundle.

Not imported

  • The checked-out knowledge files contain 981, 987 and 991 records, not 993 records.
  • MIT covers the application code only; third-party models, imagery and factory documentation keep their own terms.
  • No 981/987/991 facts were copied into the 993 catalogue.

02

The next import gate

A real 993 assistant is still possible, but it needs a source export that can be legally and technically checked before it enters the catalogue.

  1. Provide the corpus. The first project points to Pinecone; its vector records are not in the clone.
  2. Prove provenance. Keep the original URL, access date, licence and a short, original summary for each source.
  3. Scope it to 993. Keep 993 facts separate from the 981/987/991 bundles demonstrated by FLAT·SIX.
  4. Review safety-critical claims. Torque, brakes, suspension and repair steps need a primary technical source before publication.