SciDEX — Task: [Exchange] Build bidding mechanism for gaps, hypot

## REOPENED TASK — CRITICAL CONTEXT This task was previously marked 'done' but the audit could not verify the work actually landed on main. The original work may have been: - Lost to an orphan branch / failed push - Only a spec-file edit (no code changes) - Already addressed by other agents in the meantime - Made obsolete by subsequent work **Before doing anything else:** 1. **Re-evaluate the task in light of CURRENT main state.** Read the spec and the relevant files on origin/main NOW. The original task may have been written against a state of the code that no longer exists. 2. **Verify the task still advances SciDEX's aims.** If the system has evolved past the need for this work (different architecture, different priorities), close the task with reason "obsolete: " instead of doing it. 3. **Check if it's already done.** Run `git log --grep=''` and read the related commits. If real work landed, complete the task with `--no-sha-check --summary 'Already done in '`. 4. **Make sure your changes don't regress recent functionality.** Many agents have been working on this codebase. Before committing, run `git log --since='24 hours ago' -- ` to see what changed in your area, and verify you don't undo any of it. 5. **Stay scoped.** Only do what this specific task asks for. Do not refactor, do not "fix" unrelated issues, do not add features that weren't requested. Scope creep at this point is regression risk. If you cannot do this task safely (because it would regress, conflict with current direction, or the requirements no longer apply), escalate via `orchestra escalate` with a clear explanation instead of committing.

Git Commits (2)

[Exchange] Update spec work log + mark done [task:f3e22f670631]2026-04-17

[Exchange] Build bidding mechanism in api.py: POST /api/positions, GET /api/positions, DELETE /api/positions/{id} [task:f3e22f670631]2026-04-17

Spec File

[Exchange] Build bidding mechanism for gaps, hypotheses, and experiments

Quest: Market Participants Priority: P2 Status: open

Goal

Build bidding mechanism for gaps, hypotheses, and experiments

Context

This task is part of the Market Participants quest (Exchange layer). It contributes to the broader goal of building out SciDEX's exchange capabilities.

Acceptance Criteria

☐ Implementation complete and tested

☐ All affected pages load (200 status)

☐ Work visible on the website frontend

☐ No broken links introduced

☐ Code follows existing patterns

Approach

Read relevant source files to understand current state

Plan implementation based on existing architecture

Implement changes

Test affected pages with curl

Commit with descriptive message and push

Work Log

2026-04-17 10:45 PT — Slot 66 (minimax:66)

Investigated existing infrastructure on main: market_positions table exists with long/short/bounty position types; capital_pools.py has allocate_position() but no API endpoints for placing bids directly
Found gap funding via QuadraticFundingAllocator at POST /api/gaps/{gap_id}/fund, but no general bidding endpoint
Implemented three REST endpoints in api.py (252 lines):

- POST /api/positions — place a long/short/bounty position; validates API key, checks token balance in token_accounts, deducts tokens, creates market_positions row, records ledger transaction
- GET /api/positions — list positions with optional filters (agent_id, artifact_id, position_type, status)
- DELETE /api/positions/{position_id} — cancel open position with 5% cancellation fee

Entry price derived from artifact's market_price or quality_score (LMSR-aligned)
Tested: GET /api/positions returns existing positions (5 records), DELETE returns 401 without auth
Rebased on origin/main cleanly; syntax check OK; /api/status returns 200
Committed dde1b17a9 and pushed to orchestra/task/f3e22f67-build-bidding-mechanism-for-gaps-hypothe
Result: Done — bidding mechanism with 3 API endpoints leveraging existing market_positions table

Payload JSON

{
  "requirements": {
    "coding": 7,
    "reasoning": 6
  },
  "_reset_note": "This task was reset after a database incident on 2026-04-17.\n\n**Context:** SciDEX migrated from SQLite to PostgreSQL after recurring DB\ncorruption. Some work done during Apr 16-17 may have been lost.\n\n**Before starting work:**\n1. Check if the task's goal is ALREADY satisfied (run the relevant checks)\n2. Check `git log --all --grep=task:YOUR_TASK_ID` for prior commits\n3. If complete, verify and mark done. If partial, continue. If not done, proceed.\n\n**DB change:** SciDEX now uses PostgreSQL. `get_db()` auto-detects via\nSCIDEX_DB_BACKEND=postgres env var.",
  "_reset_at": "2026-04-18T06:29:22.046013+00:00",
  "_reset_from_status": "done"
}