Is a new sentencing warrant issued if the inmate is released early on parole or probation?

So Macto needs to be concerned with only warrants that change the length of the inmates incarceration?

Do parole and release warrants have a duration for when to release the inmate, a specific date, or do they just effectively say release the inmate today?

Do all inmates get a release warrant or are they normally just released at the end of their sentence warrant?

I wonder how many people among devs are actually following all those in-depth prison explanations :)

I am. And having all this new insight into justice system, I wanted to use it to escape speeding ticket I got yesterday.

Didn't work.

I am - nice to think about another domain once in a while and the challenges\solutions...

As I understood, macto was supposed to be enterprise solution sample or smth. And now it has such complex business requirements, wondering if anyone will have enough patience to look long enough to see any architecture through prison business logic.

@Giedrius: if you don't want to wait for the full series you can always go to his Github and look at his Macto code: https://github.com/ayende/Macto

@Giedrius, in my book if that happens that would be a pretty darned good architecture.

@Matthew Shapiro: well, there's not much what to see at the moment, but that is not the main issue. Main issue that domain for example is too complex and too uncommon and to understand reasoning why is made this or that in architecture you need to understand domain also. There's a reason, why blog system is common example - because domain is quite narrow and it is known to everyone. I'm not saying, that enterprise example should be blog, actually I'm sick of blog examples, because usually they are too simple for real life scenarios. I think best way for choosing theme for enterprise sample would be finding most common tasks in real life and implementing them with as simple as possible domain (but not simpler!). Most common task examples would be: - real time integration with another system - periodical integration with another system (like every 1 hour or smth.) - long running tasks (like generate report, that takes 1 hour to complete) - security model So let's say shop: there may be real time integration (payment systems), there may be periodical integration (updated shipment statuses), there's need for security model, and there's need for tools to monitor all this stuff and shop domain should be very understandable for most of developers.

@Giedrius - the problem with that is you have yet another 'fake' domain. What is needed (and it seems that Ayende is heading there) is a complex, real life scenario followed by examples/insight into how you flush out the system requirements and design an architecture suited for it. Using a shop (or some other relatively simple and common scenario) will result in exactly what Ayende is trying to avoid - demonstrating patterns and architecture for architecture sake.

Developers aren't always going to land projects/jobs in domains they are familiar with, so the fact that this is unfamiliar territory to most is actually a good thing. If anyone gets bored or is unwilling to read into the background to better understand the problem then frankly they aren't suited for the task at hand. They have to be willing to understand the domain if they have a hope at designing a proper architecture for it.

"And hourly Warrants requires that by the time the Warrant expire, you are either got a new one at court or let the Inmate go."

What about day- or month-based warrants? Should be the same, no?

This is a very interesting series, especially since the software I work is in this field, although it deals more with pre-prosecution police work than incarceration.

The biggest design problem for our company,which seems to have very little mention in these articles is the differences in the justice system between jurisdictions.

Perhaps the focus of this series is to show how to make a one off solution, or perhaps in Israel the justice system is more uniform than here in the States.

We sell a off the self product that currently has to work in all 50 states in the US, and are getting interest from abroad, and although almost every jurisdiction in the world is influenced by English common law, there are very large differences even between states in the US when it comes to the prosecution and incarceration system, specifically in the areas of the order of events, maximum time between events, grand juries, warrants, sentencing, privacy etc.

Our product currently has many switches to compensate, also there is a certain factor of convincing the agency we sell to that they should actually change their long standing SOP to one that actually works better from another jurisdiction, but in the end the laws are different, and a single code base that needs to adapt can be difficult to make perform well with customizability to each customer.

Are future goals are tending toward a DSL to allow us to change the complex statutory based business logic more quickly and per customer, and even allow the customer to update this business logic, because as we have found, the law is a constantly moving target, nearly every year statutes change that can affect hard coded business logic.

would you know if the israeli justice system is based mainly on a British (mandate holdover) or a European (Immigrants) model?

In the US we generally have 4 levels of overlapping jurisdictions, Federal, State, County, and City. Jails are county or city, prisons are state or federal. The judicial system is primarily state or federal. At the federal level we have many overlapping agencies with arrest power: FBI, DEA , ATF, US Marshall, Secret Service, DOJ, Military, Border patrol, many many more. 50 states each with multiple state level enforcement agencies, usually more broken up by type of offense, highway, fish and widlife, insurance fraud, etc. Over 3000 county governments with sheriffs and over 30,000 city governments many with police agencies, some contracting with county for law enforcement through the sheriff.

Laws can be defined at all 4 levels, although usually they are modeled after the larger jurisdiction, that is most state law is modeled after a equivalent federal law, and county/city laws are usually just minor ordinances.

Since we deal with Investigation/Enforcement, we have to deal with arrest,search, and intercept(communication monitoring) warrants, among others. So warrant for us has a approving judge, and issue date, expiration, and the narrative, or actual text of the powers granted. Of course we have a way to classify into types, because for instance a search warrant needs to be deconflicted on the location to make sure another agency or even another group inside a large agency isn't also serving the warrant at the same time or "bad" things can happen.

Even terminology between agencies is different,what one agency calls an indictment another calls a complaint or another a accusation, many of our customers demand the terms be changed in the system, even though they are equivalent, but the laws themselves are very specifically worded, and exacting semantics must be used in court filings to prevent problems.

So the customizability points that customers want are are field names and labels, workflow customization for the document routing/approval, screen/print layout, as some forms must be submitted to other agencies in a very specific format or they are rejected. Basically just about everything ;).

Some of the business rules are complex and convoluted, for instance in the state of Florida, since they still use summary UCR reporting for crime stats, which was developed in the 1930's, a male cannot be raped, we actually have a business rule in our report approval process that says if Florida UCR enabled and sex = male and offense = rape then throw an error preventing approval. Another is example is defining someone as a "gang member" as this can elevate a sentence in some jurisdictions. There is a federal recommendation that most states model after, but they make some changes to the "scoring" criteria, Such as "person arrested with other known gang members more than X times counts as Y points".

I could go on, this is definitely an interesting problem space.

Re: "European" Since many of the early founders were modernish Polish with socialist leanings, I supposed that they would have a sort of European outlook.

Usually one installation or instance per tenant, some tenants have multiple instances, when they really want isolation that they don't believe the security model can provide. Some systems are multi-tenant, usually in the same state jurisdiction, but it does complicate matters.

For customized data, since we are pretty committed to relational, and that is pretty much what the customers will take at this point (We have to fight for MSSQL over Oracle quite a bit, let alone something more exotic) and the ad-hoc query/reporting tools just aren't there otherwise. We are tending toward a table per subclass using schema separation for customer customization. Most of our competitors are just doing key-value tables or CustomField1,CustomField2 stuff.

Oren

The two major law code bases in Europe are English and Napoleonic Code; primary differences are trial by jury vs investigating magistrate, and I would guess you are English law based