tool	item	class	scope	path	today	owner	lifecycle	backup	override	migration	notes
quickchr	settings file	config	user	$TIKOCI_HOME/quickchr/quickchr.env	~/.config/quickchr/quickchr.env	quickchr src/lib/settings.ts, settings-file.ts	settings set and reset; atomic write keeping one .bak	yes	QUICKCHR_KEY per key	quickchr	Seven keys, no secrets. Windows today: %USERPROFILE%\.config\quickchr
quickchr	project settings file	config	project	PROJECT/.tikoci/quickchr/quickchr.env	- (new)	quickchr (planned)	settings set --project	no	TIKOCI_PROJECT	quickchr	Travels. Allowlisted keys only: default-channel, default-arch, timeout-extra (references/settings.md)
quickchr	personal project settings	config	project	PROJECT/.tikoci/quickchr/local/quickchr.env	- (new)	quickchr (planned)	settings set --local	no	TIKOCI_PROJECT	quickchr	Read only when the project is trusted for quickchr; then any key except the host and cache policy keys
quickchr	machine definitions (reserved)	config	project	PROJECT/.tikoci/quickchr/machines/NAME.toml	- (new)	quickchr (future)	written by people or quickchr	no	TIKOCI_PROJECT	quickchr	The path is reserved; the format and what happens when a definition changes after the machine exists are quickchr's design. TOML because people edit it. Definitions are intent, not settings: only a flag overrides a value in one (a QUICKCHR_DEFAULT_CHANNEL in a shell profile does not). Read only when trusted (a git worktree through its main checkout, so a branch can test its own definitions): provisioning scripts, disk sizes, port forwards and networks reach outside the VM. May attach to an existing host network service, never create one. A twin of a centrs device names it (LABEL:edge1) instead of copying its address
quickchr	network definitions (reserved)	config	project	PROJECT/.tikoci/quickchr/networks/NAME.toml	- (new)	quickchr (future)	written by people or quickchr	no	TIKOCI_PROJECT	quickchr	As machine definitions: reserved path, quickchr's format, read only when trusted
quickchr	machine directory	state	user	$TIKOCI_HOME/quickchr/machines/NAME/	~/.local/share/quickchr/machines/NAME/	quickchr src/lib/state.ts getMachineDir, saveMachine	deleted by remove and by a failed add; per-machine .lock/	yes	QUICKCHR_HOME; QUICKCHR_DATA_DIR keeps its meaning (whole data tree, cache included)	quickchr	machine.json, disks, qemu.log, ssh/. machine.json stays JSON and stays readable by older quickchr versions bundled in centrs, restraml and tikbook: a written promise on quickchr's side. Written in place today (atomic writes are an adoption task). Migration unit is the whole data dir, refused while any machine runs, with a symlink left at the legacy path. Windows today: %LOCALAPPDATA%\quickchr
quickchr	project machine directory	state	user	$TIKOCI_HOME/quickchr/projects/ID/INSTANCE/machines/NAME/	- (new)	quickchr (planned)	created when a trusted project's machine is realized for a checkout; listed as orphaned when no trusted project holds ID or the checkout is gone	yes	QUICKCHR_HOME	quickchr	ID is the project's identity (the main checkout's, for a worktree), so two projects' edge1 are two machines and a copy gets its own. INSTANCE is the checkout it was realized for, so two worktrees never reset one VM; a definition may opt into sharing the main checkout's. Kept off the project directory so multi-GB disks never land on a synced folder or a network share. An instance records what tells a reused worktree path from the original (SKILL.md), and quickchr prune removes gone checkouts and releases their claims. Named LABEL:edge1 from anywhere (SKILL.md, Names across scopes)
quickchr	project trust record	state	user	$TIKOCI_HOME/quickchr/projects/ID/project.json	- (new)	quickchr (planned)	written only by the trust command after a person confirms, never through MCP	yes	-	quickchr	The reference resolver's format: the project's canonical path, matched against local/id. How trust is recorded, and whether tools share one record, is open (SKILL.md)
quickchr	machine credentials	secret	user	the machine's own directory (0600), for user and project machines	~/.config/quickchr/com.quickchr.instance.json	quickchr src/lib/secrets.ts, credentials.ts	removed with the machine	yes	-	quickchr	Today keyed by machine name only, so two data dirs overwrite each other's entries; per machine directory fixes that. Kept out of the keychain on purpose: a prompt hangs non-interactive runs
quickchr	MikroTik web account	secret	user	OS keychain com.quickchr.mikrotik-web (not in a sandbox), else $TIKOCI_HOME/quickchr/com.quickchr.mikrotik-web.json	keychain, fallback ~/.config/quickchr/com.quickchr.mikrotik-web.json	quickchr src/lib/credentials.ts, secrets.ts	saved by license and the wizard; 0600	yes	--license-account, --license-password, then MIKROTIK_WEB_ACCOUNT, MIKROTIK_WEB_PASSWORD	quickchr	Never in a project. A sandbox never reads or writes the keychain
quickchr	image and package cache	cache	user	$TIKOCI_CACHE_DIR/quickchr/	~/.local/share/quickchr/cache/	quickchr src/lib/cache.ts, download.ts, images.ts	capped by cache-max-size (2 GB), oldest version first; downloads land as .part files and are renamed	no	QUICKCHR_CACHE_DIR, TIKOCI_CACHE_DIR; QUICKCHR_CACHE_MAX_SIZE; library cacheDir option	quickchr	Entries keyed by version, architecture and digest. Only the cache root's owner evicts (a sandbox only a cache inside it), with that root's size policy. Only live leases protect an entry; a stopped machine holds none. Reset and provisioning rollback fetch the factory image again by name; an offline lab keeps an opt-in pristine copy in its machine directory as state. CI caches this directory
quickchr	storage lock and leases	runtime	user	$TIKOCI_CACHE_DIR/quickchr/.storage.lock/, .storage-leases/	~/.local/share/quickchr/.storage.lock/, .storage-leases/	quickchr src/lib/storage-lease.ts	a dead holder's lease is removed	no	-	quickchr	Live only: reads, downloads and admission in flight (bytes reserved per filesystem, machine disks included), each removed when its holder dies. They move with the cache, so every scope that shares it sees them. CI cache steps exclude .storage-leases/
quickchr	port and MAC claims and allocation lock	host-wide	host	~/.tikoci/host/quickchr/ (lock and claims; quickchr's format)	~/.local/share/quickchr/.allocate.lock/	quickchr src/lib/lock.ts	lock held only while choosing; a claim is durable (a machine) or live (pid, boot id and start time), and stale claims are found and released	no	-	quickchr	The host scope: from the account's real home, moved by neither TIKOCI_HOME nor TIKOCI_SANDBOX, so sandboxes and moved user scopes register here like any run (no separate sandbox range). A bind probe still catches other accounts and programs. A container with its own home is its own host scope. Gives the move off the fixed 9100 base (quickchr#56) a place to live
quickchr	managed-network registry	host-wide	host	~/.tikoci/host/quickchr/ (quickchr's format)	- (machinesOnManagedNetwork reads one data dir)	quickchr (planned)	written when a context creates or attaches to a managed network	no	-	quickchr	Which context created which network and which machines attach, so networks remove sees attachments from every context, not only the current data dir (quickchr#256)
quickchr	named networks	state	user	$TIKOCI_HOME/quickchr/networks/NAME.json	~/.local/share/quickchr/networks/NAME.json	quickchr src/lib/socket-registry.ts	an automatically created network is removed with its last member, an explicit one persists; pid lock with a 5 s timeout	yes	-	quickchr	-
quickchr	network sockets	runtime	user	$TIKOCI_RUNTIME_DIR/quickchr/networks/NAME.SLOT.sock	~/.local/share/quickchr/networks/NAME.SLOT.sock	quickchr src/lib/socket-registry.ts	removed with the network	no	-	quickchr	Length checked at create today. The network registry records each socket path
quickchr	machine sockets and pid file	runtime	user	$TIKOCI_RUNTIME_DIR/quickchr/SHORT-ID/ (monitor, serial, qga, gdb sockets; qemu.pid)	the machine directory	quickchr src/lib/qemu.ts	unlinked on stop and before a respawn	no	TIKOCI_RUNTIME_DIR	quickchr	Moved out of the machine directory, whose length is unbounded once projects nest under it (reverses the earlier answer). machine.json records the paths, so a later command with a different env still finds a running machine. The pid record also holds the boot id and QEMU's start time or arguments. Windows uses TCP ports and named pipes instead
quickchr	boot log and failure reports	state	user	$TIKOCI_HOME/quickchr/logs/ (boot-log.ndjson, failures/)	~/.local/share/quickchr/boot-log.ndjson, failures/	quickchr src/lib/state.ts, diagnostics.ts	capped (newest 500 lines, newest 20 reports); reports survive remove	no	-	quickchr	For project machines too. A report can embed a serial log with provisioning passwords: owner-only. CI uploads it from a fixed sandbox path
quickchr	removal trash	runtime	user	$TIKOCI_HOME/quickchr/.removing/	~/.local/share/quickchr/.removing/	quickchr src/lib/state.ts	swept by the next remove	no	-	quickchr	Same filesystem as the machine directories, for the rename
quickchr	shell completions	install	user	shell completion directories unchanged; fallback copy in $TIKOCI_HOME/quickchr/completions/	shell completion directories; fallback ~/.local/share/quickchr/completions/ plus a line in the shell rc file	quickchr src/lib/completions.ts	completion install and uninstall commands	no	-	quickchr	The shell's conventions own the main locations
quickchr	macOS managed network services	host-wide	host	unchanged: /Library/LaunchDaemons/dev.tikoci.quickchr.net.SLUG.plist, /var/run/quickchr-net-SLUG.sock, /var/log/quickchr/, /opt/quickchr/	same	quickchr src/lib/vmnet-service.ts	networks create, restart and remove, through sudo	no	-	-	Root-owned and shared by every user and scope; only their registry entry is in the host scope. A sandbox or a project file may attach to one that exists, never create, restart or remove one
quickchr	askpass helper and temp files	runtime	process	os.tmpdir()	same	quickchr src/lib/scp.ts	removed by the caller; askpass directory 0700	no	TMPDIR	-	-
centrs	settings file	config	user	$TIKOCI_HOME/centrs/centrs.env	${XDG_CONFIG_HOME:-~/.config}/tikoci/centrs.env	centrs src/resolver/config-file.ts defaultSettingsPath; src/settings.ts	settings set; atomic write keeping one .bak	yes	--skip-env-file, CENTRS_SKIP_ENV_FILE skip it	centrs	Written with the default umask today; owner-only would match the CDB
centrs	project settings file	config	project	PROJECT/.tikoci/centrs/centrs.env	- (new)	centrs (planned)	settings set --project	no	TIKOCI_PROJECT	centrs	Travels. Allowlisted keys only (references/settings.md)
centrs	personal project settings	config	project	PROJECT/.tikoci/centrs/local/centrs.env	- (new)	centrs (planned)	settings set --local	no	TIKOCI_PROJECT	centrs	Read only when the project is trusted for centrs; then any key the user file allows
centrs	user CDB	secret	user	$TIKOCI_HOME/centrs/winbox.cdb	~/.config/tikoci/winbox.cdb	centrs src/devices.ts defaultCdbPath, loadCdb	created empty only at the default path, and not while the legacy CDB exists; 0600; atomic writes	yes	--cdb-file, CENTRS_CDB_FILE; password from --cdb-password, CENTRS_CDB_PASSWORD	centrs	The user's own devices. Ignores XDG_CONFIG_HOME today while centrs.env honors it, so the two can split
centrs	project CDB	secret	project	PROJECT/.tikoci/centrs/local/winbox.cdb	--cdb-file after devices init (centrs#376)	centrs src/devices.ts initCdb	created only by devices init, which also trusts the project; never auto-created	no	TIKOCI_PROJECT	centrs	Never travels: it holds credentials. Read only when trusted and local/ is private (0700, file 0600); a git worktree uses its main checkout's. The project holds centrs data when .tikoci/centrs/ exists; then a missing or unreadable CDB is an error, never the user CDB. Used instead of the user CDB for the run, never merged; the envelope names the scope, and a not-found error says when the user CDB has the name (user:home-gw). local/.gitignore (*) keeps it out of git on every branch
centrs	user-selected CDB	secret	user	unchanged: any path the user names	same	centrs src/devices.ts resolveDevicesSettings	never moved or migrated	no	--cdb-file, CENTRS_CDB_FILE	-	For example WinBox's own address book. A project file can never name one outside the project
centrs	CDB backups	secret	user	beside the CDB	beside the CDB	centrs src/data/winbox-cdb-write.ts	two newest kept	no	follows the CDB	centrs	Plaintext backups can outlive devices encrypt
centrs	CDB lock and guard	runtime	user	beside the CDB	beside the CDB	centrs src/data/winbox-cdb-lock.ts	broken only for a dead holder on the same host; the .lock.guard file is never deleted	no	follows the CDB	-	A lock lives beside the file it guards, not in the runtime root
centrs	centrs.db	state	user	$TIKOCI_HOME/centrs/centrs.db	- (planned)	centrs (planned, MATRIX)	derived and deletable; no code path may need it	no	-	centrs	Not a cache: its facts describe this user's networks
centrs	project centrs.db	state	project	PROJECT/.tikoci/centrs/local/centrs.db	- (planned)	centrs (planned, MATRIX)	derived and deletable	no	TIKOCI_PROJECT	centrs	Facts about the project CDB's devices; never travels
centrs	project trust record	state	user	$TIKOCI_HOME/centrs/projects/ID/project.json	- (new)	centrs (planned)	written by trust or devices init after a person confirms, never through MCP	yes	-	centrs	The reference resolver's format, as quickchr's. How trust is recorded is open (SKILL.md)
centrs	SNMP MIB cache (planned)	cache	user	$TIKOCI_CACHE_DIR/centrs/mib/VERSION/	- (MATRIX policy says XDG cache root)	centrs (planned, MATRIX SNMP theme)	one directory per exact RouterOS version; never another version's MIB	no	-	centrs	Immutable and per version, so every scope can share it. The 2026-06-06 policy text needs rewriting on adoption
centrs	SSH known_hosts	state	user	$TIKOCI_HOME/centrs/known_hosts, with ~/.ssh/known_hosts read after it	~/.ssh/known_hosts	centrs src/protocols/ssh.ts sshCommonOptions	StrictHostKeyChecking=accept-new adds new keys to the first file only	yes	-	centrs	UserKnownHostsFile lists both files, so keys the user already pinned still apply and centrs writes only its own. Keeps quickchr's reused 127.0.0.1:PORT keys out of ~/.ssh. A sandbox lists only its own file
centrs	SFTP staging	runtime	process	os.tmpdir()	same	centrs src/transfer.ts withTempFile	removed in finally	no	TMPDIR	-	-
centrs	corpus database (development)	cache	checkout	CHECKOUT/.cache/corpus	same	centrs scripts/corpus-fetch.ts	fetched on demand	no	CENTRS_CORPUS_DB	-	Not shipped
rosetta	managed DB generations	cache	user	$TIKOCI_CACHE_DIR/rosetta/ros-help-VERSION.db	~/.rosetta/ros-help-VERSION.db	rosetta src/paths.ts resolveDbPath; src/db-lifecycle.ts	downloaded on first run or a stale tag; read-only; evicted under an exclusive lock, keeping the running, live and newest idle versions	no	DB_PATH, then --db (a file, never a managed generation)	rosetta	Immutable and versioned, so every scope can share them. Today no variable moves the directory
rosetta	download lock and staging	runtime	user	beside the DB (.lock, .tmp.PID, .retiring-PID)	same	rosetta src/setup.ts; src/db-lifecycle.ts	lock stale after 15 minutes; leftovers swept at startup	no	follows the DB	-	Same filesystem as the DB, for the atomic rename
rosetta	legacy shared DB	state	user	stays at ~/.rosetta/ros-help.db	~/.rosetta/ros-help.db	rosetta src/db-lifecycle.ts	written by 0.11.2 and earlier; reported after 14 idle days, never deleted	no	-	rosetta	Old clients keep using it, so it is never moved or deleted automatically
rosetta	project settings file	config	project	PROJECT/.tikoci/rosetta/rosetta.env	- (new)	rosetta (optional)	written by people	no	TIKOCI_PROJECT	rosetta	An example of a small traveling file: the RouterOS version a project targets. rosetta needs no settings file today
rosetta	dev DB	cache	checkout	CHECKOUT/ros-help.db	same	rosetta src/paths.ts	built by make extract or make db-sync; never collected	no	DB_PATH, --db	-	Gitignored; untrusted until verified
rosetta	compiled-binary DB	cache	install	open: beside the executable (portable) or $TIKOCI_CACHE_DIR/rosetta/	beside the executable	rosetta src/paths.ts resolveBaseDir; src/setup.ts downloadDb	downloaded beside the binary; read-write; never collected	no	DB_PATH, --db	rosetta	Fails when the install directory is read-only. The container image keeps its DB beside the binary
rosetta	TUI history (planned)	state	user	$TIKOCI_HOME/rosetta/history	~/.rosetta/browse_history (BACKLOG)	rosetta (planned)	-	no	-	rosetta	-
vscode-tikbook	router password	secret	user	unchanged: VS Code SecretStorage	same	vscode-tikbook src/config.ts	owned by the editor	-	-	-	An extension's secrets belong in the editor's secret storage
lsp-routeros-ts	rosetta DB path setting (proposed)	config	user	rosetta's own resolution: DB_PATH, then rosetta's default	proposal defaults to ~/.rosetta/ros-help.db	lsp-routeros-ts docs/rosetta-alignment.md	-	-	-	lsp-routeros-ts	That default is rosetta's legacy shared DB; a copied path drifts, so ask rosetta
