ORCID Research Archive

Andy Oliver Rozario · ORCID 0009-0004-5072-1946 · Bangalore

Citable copy of the research behind two open-source AI systems:

Project	Role	Live / source
FutureSeer	Inspectable traditional divination (50+ systems, Ask the Seer)	futureseer.app
VassalOps	Local-first Windows desktop agent with a human bot-sitter	GitHub

This repository exists so the work has a scholarly record (ORCID, citation file, archived methodology) in addition to the product repos. It is not a replacement for those codebases.

Traditional methodology should stay public and inspectable — engines you can read, challenge, and fund as research, not black-box horoscopes.

Why this archive exists

ORCID emailed that this iD had no research outputs. The software and knowledge work already live on GitHub; they were not yet listed on the ORCID record. This repo:

1. Catalogues the outputs in ORCID-ready metadata (orcid/works.json, CITATION.cff)
2. Snapshots methodology, knowledge files, and architecture notes from the local FutureSeer and VassalOps trees
3. Explains how to add those works to orcid.org/0009-0004-5072-1946

Research outputs to add to ORCID

Add these as works on the ORCID record (see orcid/HOW_TO_ADD_WORKS.md):

Work	ORCID type	Preferred URL
FutureSeer	software	https://github.com/AndyOliverR/FutureSeer
VassalOps	software	https://github.com/AndyOliverR/VassalOps
FutureSeer occult knowledge base	data-set	sources/futureseer/knowledge/ in this repo
Astrology engine audit	working-paper	sources/futureseer/docs/ASTROLOGY_ENGINE_AUDIT.md
Multi-system prediction methodology	working-paper	sources/futureseer/docs/MULTI_SYSTEM_PREDICTION.md
Local-first HITL desktop agent	working-paper	sources/vassalops/README.md + SECURITY.md
This research archive	data-set	this repository

Full metadata: orcid/works.json · BibTeX: orcid/works.bib · Record notes: orcid/record.md

What’s in this folder

orcid/          ORCID record notes, works catalog, add-to-ORCID steps
works/          Short scholarly descriptions of each output
sources/
  futureseer/   Snapshot of knowledge/, docs/, design and agent methodology
  vassalops/    Snapshot of architecture, security, acceptable use, and docs
CITATION.cff    Machine-readable citation for GitHub

Not copied: application source, node_modules, .env files, Firebase keys, VassalOps storage/ sessions, config.local.json, or any login/secret material. The executable research lives in the public product repos.

Research thesis (short)

FutureSeer. Commercial AI horoscope apps hide how readings are produced. FutureSeer implements Vedic (sidereal Lahiri), Western (tropical), Tarot, numerology, I Ching, runes, and related systems as type-safe engines. Ask the Seer must stay inside each tradition’s rules. Chart pipeline: local birth time → UTC → tropical or sidereal. Knowledge files ground the model in traditional sources instead of generic LLM astrology.

VassalOps. Cloud agents ship enterprise screen and file context to a remote brain. VassalOps keeps planning on-device (local Ollama), allowlists desktop tools, and requires a human Approve gate before mouse/keyboard actions. Data stays local by default.

Cite

See CITATION.cff. Until a DOI is minted (Zenodo is the usual next step), cite the GitHub URL and ORCID iD.

Rozario, A. O. (2026). Inspectable AI and Traditional Divination: Research Archive.
https://github.com/AndyOliverR/orcid-research
ORCID: https://orcid.org/0009-0004-5072-1946

Contact

• ORCID: 0009-0004-5072-1946
• GitHub: AndyOliverR
• Product: futureseer.app
• LinkedIn · X

License: MIT. Knowledge and readings are educational, not medical, legal, or financial advice.

Public site (Vercel)

The archive is also a Next.js site for humans, search engines, and browser agents.

• Local: pnpm install then pnpm dev → http://localhost:3000
• Pages: /works, /papers, /knowledge, /sponsor
• Agent files: /llms.txt, /sitemap.xml, /api/works, /api/search?q=
• WebMCP (Chrome origin trial / flag): tools list_works, get_work, search_content, start_sponsor_checkout
• Payments: optional Razorpay packs ₹199 / ₹499 / ₹999. Copy env-template.txt to .env.local. Use the same RAZORPAY_KEY_ID / RAZORPAY_KEY_SECRET / NEXT_PUBLIC_RAZORPAY_KEY_ID as FutureSeer production if you want one merchant account.

Suggested production host: https://research.futureseer.app (NEXT_PUBLIC_SITE_URL). Until DNS is attached, Vercel assigns *.vercel.app.

Checkout always opens Razorpay’s hosted UI. Agents cannot complete UPI/3DS without a human. Research pages stay free.

Deploy: Vercel project from this GitHub repo, framework Next.js, env vars from env-template.txt. Then optional DNS CNAME research → Vercel.