added to-be-implemented status

We decided to implement open-ended shard interval on 2021-11-23.

1 files changed, 9 insertions, 7 deletions

diff --git a/doc/proposals/2021-11-open-ended-shard-interval.md b/doc/proposals/2021-11-open-ended-shard-interval.md
index 0cdc339..b9de1bc 100644
--- a/doc/proposals/2021-11-open-ended-shard-interval.md
+++ b/doc/proposals/2021-11-open-ended-shard-interval.md
@@ -1,10 +1,14 @@
-# Open-ended shard interval
+**Title**: Open-ended shard interval </br>
+**Date**: 2021-12-04 </br>
+**State**: To be implemented </br>
+
+# Summary
 We would like to remove `shard_end` from a log's static metadata, and instead
 have an open-ended shard-interval.  An open-ended shard interval allows an
 operator to continue its log operations without starting a new log unless it
 really necessary.  This should make it easier to maintain lists of known logs.
 
-## Details
+# Detailed description
 An operator defines how long they intend to run a log at minimum.  The log
 operator may increase this time later on but should not decrease it.  The log
 operator should give an account for how they plan to achieve said operations,
@@ -27,8 +31,6 @@ to ensure that logging requests can be performed in all active logs.
 We think that this setup could work with hard-coded, manually adjusted, and
 dynamically adjusted log policies; all with different trade-offs of course.
 
-## Other
-- We need to create a best practise document for log operations.  It would also
-be helpful for verifiers to assess if it is a good idea to rely on a log.
-- We should probably define an error that indicates that a log was toggled into
-read-only mode, in preparation of a complete shutdown.
+We may need an error that says if a log was toggled into read-only mode.  We
+will need a best-practise document for log operations that makes policy
+questions easier.  How to to think about `shard_end` goes into that document.