Subcontractor proposals

A feature for albertlane.net account holders. It lets an account holder record a proposal to do paid work for another organisation, publish it, and keep a tamper-evident history of what happened to it. It is the backend for a later Albert & Robot Operating System (AROS) app.

What these records are. Each record is an offer made by the account holder named on it. A record is not a contract and is not evidence that the counterparty agreed to anything. The counterparty did not create, sign or endorse these pages. The counterparty signature stays blank until the counterparty provides one. Only the account holder who made a record can change its status, and every change is added to an append-only, hash-chained history.

Published proposals

ProposalOffered byCounterpartyStatusCounterparty signatureRecorded (UTC)
Proposal: Transfer Portal infrastructure — Bluetooth mesh / Matter secured on-chain payments between albertlane.net accounts and X Money (Albert Lane, 10/29/26)Albert LaneOpen — no counterparty namedOffered — not yet sent / not accepted by any partyblank — pending2026-10-29T22:43:14.189Z
Proposal: paid backend development for xAI API integrations (Albert Lane, albertlane.net)Albert LanexAIOffered — not yet sent / not accepted by xAIblank — pending2026-10-29T22:18:37.903Z

API

GET /api/subcontractor/proposalspublic — published proposals
GET /api/subcontractor/proposals/:idpublic — one published proposal with its body, SHA-256 and event history
POST /api/subcontractor/proposalsaccount holders — create a proposal (Bearer: albertlane.net account token)
POST /api/subcontractor/proposals/:id/statusthe proposal's owner only — change status or publish/unpublish
GET /api/subcontractor/proposals/:id/addendapublic — addenda and the addenda policy
POST /api/subcontractor/proposals/:id/addendathe proposal's owner only — append an addendum (JSON: body, optional summary)
GET /api/subcontractor/proposals/:id/addenda/:seq.txt · .otspublic — raw addendum text (byte-exact) and its OpenTimestamps proof

Addenda policy (all accounts)

Addenda policy: max 2, within 60 days of publication. An account holder may append at most 2 addenda to a proposal, and only within 60 days of the proposal being recorded. Addenda are append-only and hashed; the original proposal text and its SHA-256 never change. Requests past the limit or the window are refused (HTTP 409).

Sign-in uses your existing albertlane.net account: an id.albertlane.net access token, an AROS account key, or an AROS session token. This feature is on by default for every account.

For account holders

Change status (owner only)