Store
Store commands let you write and read local key/value data from the terminal. The command group is:
softadastra storeCommands
softadastra store put <key> <value>
softadastra store get <key>Show store help
Run:
softadastra storeOutput:
Softadastra store
Usage
softadastra store put <key> <value>
softadastra store get <key>
Commands
put Write a key/value pair
get Read one keyWrite a value
Use store put to write a local value.
softadastra store put app/name SoftadastraWhen the write succeeds, the CLI prints the key, version, and mutation status.
Example output:
✓ Stored value.
Field Value
key app/name
version 1
status createdIf the key already exists, the status can be updated.
softadastra store put app/name "Softadastra Runtime"Example output:
✓ Stored value.
Field Value
key app/name
version 2
status updatedIf the value did not change, the status can be unchanged.
Read a value
Use store get to read one local value.
softadastra store get app/nameExample output:
Store entry
Field Value
key app/name
value Softadastra
version 1
timestamp 1760000000000The exact version and timestamp depend on your local runtime.
Keys
A key identifies a local value.
Good examples:
app/name
settings/theme
profile/name
message/1
cache/sessionUse stable and readable keys. A good pattern is:
domain/name
domain/id/fieldExamples:
profile/name
settings/theme
files/docs/readme.txtAn empty key is invalid.
softadastra store put "" valueExpected error:
Key cannot be empty.Values
A value is the data stored under a key.
Examples:
softadastra store put profile/name Ada
softadastra store put settings/theme dark
softadastra store put message/1 helloWhen a value contains spaces, quote it:
softadastra store put app/title "Softadastra Runtime"Local-first behavior
Store commands work locally. This command does not need a remote server:
softadastra store put draft/1 helloAnd this command reads from the local store:
softadastra store get draft/1Peers, discovery, and transport are not required for local store commands. That is the main idea: local work should be useful before the network is available.
Store and sync
A store write can create local work that sync can later process. A simple flow is:
softadastra store put app/name Softadastra
softadastra sync status
softadastra sync tickstore put writes locally.
sync status shows what the sync pipeline is tracking.
sync tick moves the sync pipeline forward once.
Example workflow
Write a value:
softadastra store put app/name SoftadastraRead it back:
softadastra store get app/nameCheck sync:
softadastra sync statusRun one sync tick:
softadastra sync tickRead the value again:
softadastra store get app/nameInteractive mode
Inside interactive mode, do not repeat softadastra.
Start the CLI:
softadastraThen run:
softadastra> store put app/name Softadastra
softadastra> store get app/name
softadastra> sync status
softadastra> sync tick
softadastra> exitCommon errors
Missing key or value
This happens when store put does not receive both arguments.
softadastra store put app/nameOutput:
Missing key or value argument.
Usage: store-put <key> <value>Fix:
softadastra store put app/name SoftadastraMissing key
This happens when store get does not receive a key.
softadastra store getOutput:
Missing key argument.
Usage: store-get <key>Fix:
softadastra store get app/nameEmpty key
This happens when the key is empty.
softadastra store put "" valueOutput:
Key cannot be empty.Use a non-empty key:
softadastra store put app/name valueKey not found
This happens when the key does not exist in the local store.
softadastra store get missing/keyOutput:
Key not found: missing/keyThis is not a crash. It only means the local store does not have that key.
Unknown store command
If you run an unsupported store command:
softadastra store remove app/nameThe CLI returns:
Unknown store command: remove
Usage: store <put|get>For now, use:
softadastra store put <key> <value>
softadastra store get <key>Good first test
Run:
softadastra store put app/name Softadastra
softadastra store get app/name
softadastra sync status
softadastra sync tickThis tests local write, local read, sync inspection, and one manual sync step.
Summary
Use:
softadastra store put <key> <value>to write a local value.
Use:
softadastra store get <key>to read a local value. Store commands are local-first. They do not need peers, discovery, transport, or a remote server to be useful. Next, continue with Sync.