From 1d12b8bb8470b51f1cb36386e42a1b1b591f978a Mon Sep 17 00:00:00 2001
From: Flancian <0@flancia.org>
Date: Sun, 21 Aug 2022 18:47:17 +0200
Subject: [PATCH] autopushed

---
 agora pkg chapter.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/agora pkg chapter.md b/agora pkg chapter.md
index d43d80522..ec5b26782 100644
--- a/agora pkg chapter.md	
+++ b/agora pkg chapter.md	
@@ -364,13 +364,17 @@ Here we cover some details of the provided free and open source reference Agora
     - User controlled [[git]] repositories are the default data source.
   - [[agora server]] provides a UI supporting querying and composition and [[json]], [[rss]], [[rdf]] endpoints.
     
-### Data model
+### Data ownership model
 - Users can contribute [[repositories]] to an Agora.
   - To do so, they publish their resources to a repository they control and then they let an Agora know of their intention to integrate, a desired username and their agreement with an Agora's contract.
   - [[git]] repositories are the default data source, with other repository providers ([[http]], [[ipfs]], [[drive]], [[dropbox]]) to follow.
 - Users can contribute individual [[resources]] to an Agora.
   - As of the time of writing they can interact with an Agora system account (i.e. bot) in supported platforms like [[twitter]] and [[mastodon]] while indicating nodes they want to attach to using a Layer 1 convention.
   - (Soon they will be able to submit this information directly on the [[agora server]] provided interface.)
+- Whenever a user signals [[opt in]] to remote writing (bridging, siphoning, cross posting), [[an Agora]] does its best to guarantee user data ownership.
+  - By default, an Agora will not store data for the user if it the user has not signaled a strong enough intent to write full data. Instead, an Agora will try to [[link]] to resources only in matching contexts, allowing users to recover resources without meddling in data management (see [[go links]] study case).
+
+### Endpoints
 
 # Thanks