Skip to content

[P1] Align PRD treasury wording with current operator-direct model #139

@ametel01

Description

@ametel01

Problem

Most treasury/signer separation language is already aligned in the live docs (README.md, docs/spec.md), and contract behavior already routes payments directly to immutable operator private balance.

Remaining mismatch is in PRD wording that can still imply unavailable treasury controls (e.g. moving accumulated user-paid tokens from contract balance to a designated treasury address).

Also, original validation scope referenced contracts/credit_fpc/src/main.nr, which no longer exists.

Scope

Narrow this task to docs alignment for current Alpha behavior:

  • Update local-docs/fpc-prd.md to explicitly reflect current model:
    • fees are paid user private -> operator private directly
    • no on-chain treasury sweep from contract token balance
    • signer/revenue destination are the same operator identity in Alpha
  • Remove stale references to removed contract variants/paths in this issue and related wording.
  • Optional: add a brief cross-reference note from PRD section to docs/spec.md (limitations/security) for canonical behavior.

Files to change

  • local-docs/fpc-prd.md
  • (optional) small cross-reference touch-up in README.md or docs/spec.md

Validation

  • Cross-check against contracts/fpc/src/main.nr transfer destination and immutable config model.
  • Confirm no remaining PRD language implies unavailable on-chain treasury controls for current Alpha.

Acceptance Criteria

  • PRD text no longer implies unsupported treasury sweep/admin controls.
  • Alpha separation model is explicit: no signer/treasury split on-chain in current design.
  • Issue/docs scope no longer references removed credit_fpc path.

Depends on

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:contractsProject workflow label: area:contractsarea:toolingProject workflow label: area:toolingcomponent:securityProject workflow label: component:securitydocumentationImprovements or additions to documentationpriority:BProject workflow label: priority:Bsize:SProject workflow label: size:Stype:taskProject workflow label: type:task

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions