SPEP: <SPEP number>
Title: <SPEP title>
Author: <list of authors' real names and optionally, email addresses>
Type: <Standard Track | Informational | Process>
Status: <Draft | Review | Accepted | Implementation | Final | Deferred | Rejected | Withdrawn | Replaced>
Created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
Updated: <date last updated, in ISO 8601 (yyyy-mm-dd) format>
Discussions-To: <URL of discussion thread>
Replaces: <SPEP number>
Replaced-By: <SPEP number>
<A short (~200 word) description of the technical issue being addressed>
<The rationale fleshes out the specification by describing why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other AI framework>
<Detailed description of the problem being addressed, including severity and affected users>
<Market analysis, target customers, potential business models, and ROI estimates>
<The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current SpoonOS platforms>
<All SPEPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal>
<For a SPEP that adds new functionality or changes language behavior, it is helpful to include a section on how to teach users, new and experienced, how to apply the SPEP to their work. This section may include key points and recommended documentation changes that would help users adopt a new feature or migrate their code to use a language change>
<The reference implementation must be completed before any SPEP is given status "Final", but it need not be completed before the SPEP is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code>