NASA-IMPACT / NASA-IMPACT/akd-core
PSI Agent: Tool Hosting & Deployment (PSI↔AKD alignment)
@rohit-sahoo is already working on this.
Since Aug 21, 2026.
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
PSI Agent: Tool Hosting & Deployment
Tracking · Parent EPIC: #377 — PSI Agent · Tool scope: #500 · Tool build: #503 · PI: 26.4 Agent Development
Collaboration: NASA PSI (Physical Science Informatics) team
Context
Once the PSI agent tools are built and validated in the fast-iteration space (#503, in nasa-impact/akd-ext), the open question is where they should actually live and run long-term. akd-ext is a prototyping ground, not a production home.
Answering this needs a discussion between the PSI and AKD teams — it's as much an ownership/operations decision as a technical one, and it depends on PSI's infrastructure, data access, and who maintains what.
What this issue covers
- Align PSI↔AKD on the permanent hosting home for each PSI agent tool (AKD-side, PSI-side, or hybrid).
- Decide the build/operate ownership split — who maintains each tool once it leaves akd-ext.
- Confirm data & access in the target environment (PSI data sources, credentials, network reach).
- Plan the migration of the validated tools out of
nasa-impact/akd-extinto their agreed home. - Deploy the tools there and confirm the PSI agent reaches them in the target setup.
Done when
- Hosting home for each tool agreed with the PSI team.
- Ownership / maintenance split (AKD vs PSI) agreed and documented.
- Data/access validated in the target environment.
- Tools migrated out of akd-ext and deployed to the agreed home.
- PSI agent invokes the tools in the target/production setup; validated end-to-end.
Depends on
- #503 — tools built & validated in akd-ext (this decision is informed by what the build learns).
- #500 — tool scope (the hosting / ownership questions originate there).
Blocked by
- ⛔ PSI↔AKD discussion on hosting & ownership. Needs input from the PSI team; not fully actionable until the tools are built and that conversation happens.
Out of scope
- Building the tools — covered by #503.
- Full-agent deployment (the PSI agent itself, beyond its tools) — broader EPIC #377 concern.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.