How Techne works
Five layers, each with one job. Here is Maya's park passing through all five.
pub.techne.draft.placeAdded by maya.techne.town, in Bouldertechne.townShow codeWritten to their PDS
com.atproto.repo.applyWritesWritten to their PDS.
The person signs in with their atproto account, maya.techne.town. Your app builds the record with Place.create and techne.put writes it to their repo, not to techne.computer.
techne.pubShow codeChecked against place.draft.techne.pub
Place.validateChecked against its shape on techne.pub.
The type lives at place.draft.techne.pub. The same check runs in your app and on techne.computer.
techne.computerShow codeIndexed by techne.computer; its space decides who reads
sync.indexRecordIndexed by techne.computer; spaces decide who reads.
techne.computer indexes each version and marks it valid, pending or invalid. A place has a public home; a private record lives in a space, whose read policy decides who reads it.
techne-sdkShow codeRead with techne.query
query.listRecordsRead with techne.query or techne.get.
A read is a query document; Place.query builds one, typed to the place's roles. Every read answers items, each with its uri and record.
Shown in Commons
commons.techne.computerShown in Commons and Beacon.
Commons lists the park in its directory; Beacon offers it as somewhere to meet. Both use the same hooks from techne-sdk/react.
Eben G. Fine Park
Click a layer to see its code.