security(vault): establish user-unlocked cryptographic vault substrate

Open
#301 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript
Domain
cryptography, databases, security

Research direction

Start by reading the parent tracker #278 and confirming that prerequisite #238 is merged before implementation begins. This issue is still a spec shell covering the key hierarchy, vault metadata database, encrypted envelope/blob primitives, opaque index tokens, unlock gate, and cross-tab contracts; done means those contracts are established without production migration or lock UI.

Written by the indexing model from the issue text.

Description

agent:spec-in-progress difficulty:critical enhancement lane:spec

Status: spec-in-progress\nParent tracker: #278\nPrerequisite: #238 must be merged before implementation starts.\n\nSpec shell. Owns the cryptographic key hierarchy, vault metadata database, encrypted envelope/blob primitives, opaque index tokens, runtime unlock gate, and cross-tab coordination contracts. No production data migration or lock UI in this child.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1d 7h
Merged PRs (30d)
29

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from digidem/comapeo-cloud-app

All issues in digidem/comapeo-cloud-app

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.